Fix SKILL.md frontmatter: move version to metadata#6
Merged
fedorov merged 1 commit intoImagingDataCommons:mainfrom Feb 2, 2026
Merged
Conversation
Claude skill uploader only allows name, description, license, allowed-tools, compatibility, and metadata as top-level keys.
Contributor
Author
Member
|
Thank you @andinet for the contribution, and sorry for the delay in merging this. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The version key in the SKILL.md YAML frontmatter is a top-level property, which causes an upload error in Claude's skill uploader:
unexpected key in SKILL.md frontmatter: properties must be in ('name', 'description', 'license', 'allowed-tools', 'compatibility', 'metadata')
This PR moves version under the metadata block, which accepts arbitrary keys.