Add required name field to skills frontmatter#11
Add required name field to skills frontmatter#11krubenok wants to merge 4 commits intoastral-sh:mainfrom
Conversation
|
Please merge this! Can't install with vercel-labs/skills CLI until the frontmatters are fixed. |
|
@zanieb hopefully this is a pretty easy one to merge if you have a moment to take a look. Totally forgot about this PR thanks Conor 👍 |
|
|
||
| ```bash | ||
| /plugin marketplace add ./claude-code-plugins | ||
| /plugin marketplace add ./.claude-plugin/marketplace.json |
There was a problem hiding this comment.
This seems unrelated. This is after cloning without changing directories so the path won't work. The current example worked for me.
There was a problem hiding this comment.
Weird. I can still repro the original version not working. Edit: slightly dense moment
I think the patch is correct since the intent is to add the local instance of the marketplace and the folder in the repo is indeed called claude-plugin The detail is in the examples from Claude's error output;
Examples:
• owner/repo (GitHub)
• git@github.com:owner/repo.git (SSH)
• https://example.com/marketplace.json
• /path/to/marketplace
Since contributors to the repo should use the local one, a relative path is appropriate, but general consumption should use /plugin marketplace add astral-sh/claude-code-plugins to get the latest from GitHub.
Per the Agent Skills specs, a
nameand adescriptionfield are both required in the frontmatter of aSKILL.mdfile.In Claude Code, it seems like the required
namefield is not being enforced, but after installing the skills in codex, I would get the following error:This was confirmed as well with the
skills-ref validateCLI (which itself is perhaps a good candidate to run in CI alongside the Prettier issue in #2)After the changes, the skills load without issue in Codex and pass the validator. I also added the optional author and license metadata which helped me distinguish this from a similarly named skill I had written myself before and a small correction to the CONTRIBUTING.md file. Per the specs the metadata fields should not be provided to the models so it's purely organizational.