agentleFS
odere-proodere-pro/claude-software-3-0-marketplace/.claude/skills/vet-plugin/SKILL.md

vet-plugin

Skill2 starsChanged 6 months agoMITView on GitHub

Author-only read-only preflight for the odere-pro marketplace repo. Checks whether a candidate repo is ready to list — owner is odere-pro, it has a valid plugin.json with name/description/license, it ships no marketplace.json of its own, and it isn't already listed — and reports go/no-go with blockers. Makes no edits. Invoke explicitly as /vet-plugin <repo>. Run before /add-plugin.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read-only preflight for a candidate plugin.

    line 16

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

/vet-plugin

Read-only preflight for a candidate plugin. Reports whether it can be listed and, if not, exactly why. Edits nothing — use /add-plugin to actually list it.

$ARGUMENTS is the candidate repo (<repo> defaults the owner to odere-pro, or owner/repo).

Steps

  1. Run bash .claude/skills/add-plugin/scripts/vet-candidate.sh $ARGUMENTS.
  2. Parse the JSON verdict and report:
    • Ready (ok: true) → show the entry it would produce (name, repo, description, license, keywords) and suggest /add-plugin $ARGUMENTS.
    • Blocked (ok: false) → list each blockers[] item with the fix. For "still ships marketplace.json", point to docs/adding-plugins.md and the oop/calibration-style removal.

Failure handling

This skill is read-only — it edits no files, so there is nothing to roll back. If vet-candidate.sh errors (exit 2: missing argument or gh/jq not installed, or a gh auth/network failure), report the error and stop; no working-tree state changed. The actual listing change happens only under /add-plugin, which carries its own rollback.

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.