fix(skill): use block-style YAML for SKILL.md metadata#197
Conversation
The metadata block was a JSON-style flow mapping with trailing commas. The Agent Skills reference validator (skills-ref) rejects that as invalid YAML frontmatter, so the skill fails the agentskills.io standard that downstream registries check against. Rewrite it as block-style YAML. The data is the same; only the serialization changes.
|
@Giri-Aayush is attempting to deploy a commit to the Vezures Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdated ChangesSKILL frontmatter metadata update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What
The
metadatablock inwebsite/public/SKILL.md(the canonical skill file, served attiny.place/SKILL.mdand symlinked fromsdk/SKILL.md) was written as a JSON-style flow mapping with trailing commas. The Agent Skills reference validator rejects it:This rewrites the block as plain block-style YAML. The data is unchanged.
Why
agentskills.io is the open SKILL.md standard, and several downstream skill registries validate submissions with
skills-ref. The flow-mapping frontmatter fails that check even though looser parsers (theskillsCLI, ClawHub) accept it today, so the skill could not pass automated validation.Verification
skills-ref validatepasses after the change:metadata.openclawinstall spec (deep-equality check passed). Only the YAML serialization changed.sdk/SKILL.mdand the servedtiny.place/SKILL.mdboth resolve to this file, so they pick up the change with no extra edits.Summary by CodeRabbit