validate-marketplace
Skill4 starsChanged 7 months agoMITView on GitHub
Validate the marketplace structure and catalog. Use before committing or releasing changes.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- felipeelias/claude-marketplacetheir own version, first seen Nov 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- felipeelias/claude-marketplace★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-pluginSkill
- link-for-testingSkill
- update-pluginSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
If everything passes, confirm the marketplace is ready to publish.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Validate the marketplace repo by running:
make validateReport the result. If validation fails, summarize the failing checks and the files involved.
The deterministic validator checks:
Claude Code marketplace (.claude-plugin/):
.claude-plugin/marketplace.json— valid JSON, required fields (name,owner,plugins), all plugin entries havenameandsource- Each local plugin source path exists on disk
- Any
skills/*/SKILL.mdfiles have valid YAML frontmatter withnameanddescription - Any
agents/*.mdfiles have valid frontmatter
Cursor marketplace (.cursor-plugin/):
5. .cursor-plugin/marketplace.json — valid JSON, required fields (name, owner, metadata, plugins), all plugin entries have name and source
6. Each local plugin source path in .cursor-plugin/marketplace.json exists on disk
7. Each plugin directory has .cursor-plugin/plugin.json with required fields: name, displayName, version, description, author, license
8. Plugin names in .cursor-plugin/marketplace.json match those in .claude-plugin/marketplace.json
- Skill counts in marketplace descriptions and README match the actual
skills/*/SKILL.mdinventory - Skill frontmatter
namematches the containing skill directory - Plugin README skill counts and listed skill rows match the plugin's skill inventory
If everything passes, confirm the marketplace is ready to publish.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

