Skip to content

fix: move version to metadata in SKILL.md frontmatter#83

Closed
mvanhorn wants to merge 1 commit into
blader:mainfrom
mvanhorn:fix/41-version-frontmatter-key
Closed

fix: move version to metadata in SKILL.md frontmatter#83
mvanhorn wants to merge 1 commit into
blader:mainfrom
mvanhorn:fix/41-version-frontmatter-key

Conversation

@mvanhorn
Copy link
Copy Markdown
Contributor

@mvanhorn mvanhorn commented Apr 4, 2026

Claude Code's skill parser rejects version as a top-level frontmatter key. The allowed set is: name, description, license, allowed-tools, compatibility, metadata.

This moves version: 2.5.1 under a metadata: block so the skill loads without the "unexpected key" error (#41, also reported in #8).

Also updates WARP.md's versioning section to reflect the new location.

Fixes #41

This contribution was developed with AI assistance (Codex).

Move `version: 2.5.1` from a top-level frontmatter key to the
`metadata:` block. Claude Code's skill parser only allows specific
top-level keys (name, description, license, allowed-tools,
compatibility, metadata) and rejects `version` at the root.
@blader
Copy link
Copy Markdown
Owner

blader commented May 27, 2026

Thanks! Closing this one. We've removed WARP.md (replaced with a tool-neutral AGENTS.md), so the WARP versioning note here no longer applies, and we're keeping the version field at the top level of the SKILL.md frontmatter rather than moving it under metadata. Appreciate the cleanup instinct though.

@blader blader closed this May 27, 2026
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.

unexpected key in SKILL.md frontmatter

2 participants