Skip to content

fix(entity-resolution): YAML parse error in description#35

Merged
jdanielmyers merged 1 commit into
mainfrom
fix/entity-resolution-yaml
May 22, 2026
Merged

fix(entity-resolution): YAML parse error in description#35
jdanielmyers merged 1 commit into
mainfrom
fix/entity-resolution-yaml

Conversation

@jdanielmyers
Copy link
Copy Markdown
Member

Summary

Fixes a YAML parse error in skills/entity-resolution/SKILL.md. The description field was a single line containing Triggers: — YAML parses internal : followed by space as a mapping key, breaking the frontmatter.

$ python3 -c "import yaml; yaml.safe_load(open('skills/entity-resolution/SKILL.md').read().split('---')[1])"
yaml.scanner.ScannerError: mapping values are not allowed here
  in "<unicode string>", line 4, column 475

Fix

Convert description: to a folded block scalar (>-). YAML treats the body as a single string regardless of internal :. No semantic change — the description text is identical when joined.

Test plan

  • python3 -c "import yaml, re; yaml.safe_load(re.match(r'^---\\\\s*\\\\n(.*?)\\\\n---', open('SKILL.md').read(), re.DOTALL).group(1))" parses cleanly
  • All required frontmatter keys present: author, description, language, name, prompt, status, summary, title, tools, type
  • No body content changes

The description value contained 'Triggers:' which YAML parses as a new
mapping key. Convert to a folded block scalar (>-) so internal colons
are treated as literal characters.
@jdanielmyers jdanielmyers merged commit 12ab2e8 into main May 22, 2026
1 check passed
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