agentleFS
ubie-ossubie-oss/claude-code-plugin/.claude/skills/plugin-verification/SKILL.md

plugin-verification

Skill1 starsChanged 9 months agoApache-2.0View on GitHub

Verify Claude extensions and plugins across hooks, skills, sub-agents, teams, manifest, structure, runtime loading, and CI parity.

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
  1. Distinctive:

    Run layered verification for extension components and plugin packaging before CI and release.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Plugin Verification

Run layered verification for extension components and plugin packaging before CI and release.

Validation Levels

  1. Component-level verification (hooks, skills, sub-agents, teams).
  2. Manifest JSON + schema checks.
  3. Directory and file layout checks.
  4. CLI load and visibility checks.
  5. Docker smoke-test parity with CI.

Progressive Disclosure

  • Validation level model: references/validation-levels.md
  • Troubleshooting guide: references/common-issues.md
  • CLI command reference: references/cli-commands.md
  • CI/CD alignment: references/ci-integration.md
  • Hook verification guidance: references/verify-hooks.md
  • Skill verification guidance: references/verify-skills.md
  • Sub-agent verification guidance: references/verify-subagents.md
  • Team verification guidance: references/verify-teams.md
  • Level 2 script: scripts/verify-manifest.sh
  • Level 3 script: scripts/verify-structure.sh
  • Level 4 script: scripts/verify-load.sh
  • Level 5 script: scripts/verify-ci.sh
  • All levels: scripts/verify-all.sh
  • Checklist: assets/checklists/verification-checklist.md
  • Mistake guide: assets/checklists/common-mistakes.md

Related Skills

  • Umbrella guide: ../implement-claude-extensions/SKILL.md
  • Hooks implementation: ../implement-hooks/SKILL.md
  • Agent Skills implementation: ../implement-agent-skills/SKILL.md
  • Sub-Agent implementation: ../implement-sub-agents/SKILL.md
  • Agent Team implementation: ../implement-agent-teams/SKILL.md
  • Plugin packaging: ../implement-plugin/SKILL.md

Sources

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.