Skip to content

fix(paper2assets): make SKILL.md description valid YAML for strict parsers - #27

Open
YQGHL wants to merge 1 commit into
microsoft:mainfrom
YQGHL:fix/paper2assets-yaml-frontmatter
Open

fix(paper2assets): make SKILL.md description valid YAML for strict parsers#27
YQGHL wants to merge 1 commit into
microsoft:mainfrom
YQGHL:fix/paper2assets-yaml-frontmatter

Conversation

@YQGHL

@YQGHL YQGHL commented Aug 5, 2026

Copy link
Copy Markdown

Problem

The description field in paper2assets/SKILL.md is a single plain scalar containing metadata.json: title / authors / .... The colon-space sequence is interpreted by strict YAML parsers as a nested mapping inside a compact mapping:

Nested mappings are not allowed in compact mappings at line 2, column 14

Claude Code and Codex tolerate this (lenient parsing), but tools that validate against the Agent Skills spec — such as Pi — refuse to load the skill.

Fix

Convert description to a folded block scalar (>) with identical content. Colons inside a block scalar are literal, so metadata.json: title / ... no longer parses as a nested mapping.

Impact

  • No content change — the description text is byte-identical after folding (verified: 965 chars, word-for-word identical).
  • Makes the skill load correctly on strict YAML / Agent Skills parsers while remaining compatible with Claude Code and Codex.

…rsers

The frontmatter description was a single plain scalar containing 'metadata.json: title / authors / ...'. The colon-space sequence makes strict YAML parsers treat it as a nested mapping inside a compact mapping, raising 'Nested mappings are not allowed in compact mappings'.

Claude Code and Codex tolerate this, but tools validating against the Agent Skills spec (e.g. Pi) fail to load the skill. Convert the description to a folded block scalar (>) with identical content, so colons stay literal.
@YQGHL
YQGHL force-pushed the fix/paper2assets-yaml-frontmatter branch from 38a7836 to f29d726 Compare August 5, 2026 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant