agentleFS
felipeeliasfelipeelias/claude-marketplace/skills/validate-marketplace/SKILL.md

validate-marketplace

Skill1 starsChanged 7 months agoMITView on GitHub

This skill should be used when the user asks to "validate the marketplace", "check marketplace sync", "verify plugin manifests", "validate marketplace.json", or mentions marketplace validation or plugin sync issues.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. PierrickMartos/Leadership-Skills★ 4same 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 repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run each check in order. Report all issues found, then summarize pass/fail.

    line 12
  2. Very specific:

    Verify .claude-plugin/marketplace.json exists and contains valid JSON with these required fields:

    line 16
  3. Very specific:

    If a plugin directory contains .claude-plugin/hooks.json, verify:

    line 58

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Validate Marketplace

Validate that marketplace.json plugin entries are in sync with their corresponding plugin.json manifests and that all files follow required conventions.

Validation Checks

Run each check in order. Report all issues found, then summarize pass/fail.

1. Marketplace Structure

Verify .claude-plugin/marketplace.json exists and contains valid JSON with these required fields:

  • $schema — must reference the Anthropic marketplace schema
  • name — marketplace name in kebab-case
  • owner — object with name (and optionally email)
  • plugins — non-empty array

2. Plugin Entry Completeness

For each entry in plugins[], verify these fields are present:

FieldRequiredNotes
nameYeskebab-case
sourceYesrelative path starting with ./plugins/
descriptionYesnon-empty string
versionRecommendedsemver format
authorRecommendedobject with name
categoryRecommendedone of: development, productivity, security, database, testing
licenseRecommendede.g. MIT, Apache-2.0

3. Plugin Source Exists

For each plugin entry with a relative source path, verify:

  • The directory at source exists
  • It contains .claude-plugin/plugin.json

4. Manifest Sync

For each plugin, compare the marketplace.json entry against the plugin's own plugin.json. Flag mismatches in:

  • name
  • description
  • version
  • author.name
  • license

The plugin.json is the source of truth. If values differ, recommend updating marketplace.json.

5. Hooks Validation

If a plugin directory contains .claude-plugin/hooks.json, verify:

  • Valid JSON
  • Has a hooks object containing at least one event key
  • Event keys are valid: PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification

Output Format

Present results as a checklist:

## Marketplace Validation Results

- [x] Marketplace structure valid
- [x] Plugin entries complete (N plugins)
- [ ] Manifest sync — version mismatch for "plugin-name" (marketplace: 0.1.0, plugin: 0.2.0)
- [x] Hooks configuration valid

End with a summary: total checks passed, total warnings, total errors.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.