Source
Verified at openai/skills commit 49f948faa9258a0c61caceaf225e179651397431.
Reproduction
The Notion knowledge-capture reference examples contain People-property values that are neither valid JSON nor resolvable Notion user identifiers:
reference/documentation-database.md:
reference/decision-log-database.md:
"Deciders": [tech_lead, architect]
"Stakeholders": [eng_team]
The current Notion page-creation schema accepts People arrays as strings/IDs; the skill has no step that resolves these symbolic names to user IDs or page URLs. Copying the examples as written either fails JSON parsing or submits unusable values.
Expected behavior
Reference payloads should be valid JSON and should explain how to resolve People values before a write.
Actual behavior
The examples look executable but contain unquoted symbolic placeholders with no identity-resolution contract.
Proposed narrow fix
Use explicit quoted placeholders such as <notion-user-id> and label the snippets as templates, or add a preceding identity lookup/resolution step and insert the returned IDs. Do not infer a person from a display name when more than one match exists.
Acceptance test
- Parse every fenced JSON payload in the Notion reference files.
- Reject unquoted symbolic values.
- For People properties, require either concrete fixture IDs or a documented placeholder syntax plus an identity-resolution step.
- Include an ambiguity fixture that must stop rather than choose a user.
No Notion workspace content was read or written for this report.
Source
Verified at
openai/skillscommit49f948faa9258a0c61caceaf225e179651397431.Reproduction
The Notion knowledge-capture reference examples contain People-property values that are neither valid JSON nor resolvable Notion user identifiers:
reference/documentation-database.md:reference/decision-log-database.md:The current Notion page-creation schema accepts People arrays as strings/IDs; the skill has no step that resolves these symbolic names to user IDs or page URLs. Copying the examples as written either fails JSON parsing or submits unusable values.
Expected behavior
Reference payloads should be valid JSON and should explain how to resolve People values before a write.
Actual behavior
The examples look executable but contain unquoted symbolic placeholders with no identity-resolution contract.
Proposed narrow fix
Use explicit quoted placeholders such as
<notion-user-id>and label the snippets as templates, or add a preceding identity lookup/resolution step and insert the returned IDs. Do not infer a person from a display name when more than one match exists.Acceptance test
No Notion workspace content was read or written for this report.