plugin-authoring
Skill0 starsChanged 3 days agoMITView on GitHub
Use when packaging skills, commands, agents, or hooks into a Claude Code plugin and publishing to a marketplace. Get the directory structure, plugin.json and marketplace.json manifests, version bump, and local-test loop right so the plugin installs cleanly and is version-pinnable.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- virajp/claude-pluginstheir own version, first seen Nov 4, 2026
- iap/hermes-guidetheir own version, first seen Nov 1, 2026
- NazmusSayad/skillstheir own version, first seen Oct 13, 2026
- eehrich/ScarabHivetheir own version, first seen Oct 9, 2026
- nafeeur/MaskShifttheir own version, first seen Sep 12, 2026
- polyant-ai/polyanttheir own version, first seen Sep 11, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- polyant-ai/polyant★ 10same name
- iap/hermes-guide★ 6same name
- eehrich/ScarabHive★ 2same name
- nafeeur/MaskShift★ 2same name
- NazmusSayad/skills★ 2same name
- virajp/claude-plugins★ 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 repository108 other files it gives its agents.
- adaptive-estimationSkill
- adaptive-loop-budgetingSkill
- adopt-and-deleteSkill
- adversarial-reviewSkill
- agent-drives-uiSkill
- agentic-coding-loopSkill
- agent-otel-trajectorySkill
- agents-as-iac-modulesSkill
- ascii-ui-mockupsSkill
- authoring-html-emailSkill
- authoring-skills-vs-mcpSkill
- batched-ssh-enumerationSkill
- c4-architectureSkill
- challenge-the-premiseSkill
- codegraph-bootstrapSkill
- codegraph-worktree-startupSkill
- colocated-pod-tolerationsSkill
- command-creatorSkill
- complexity-budgetsSkill
- connector-readinessSkill
- context-anchored-patchingSkill
- continuous-issue-resolutionSkill
- credential-proxySkill
- criticality-tiered-reportingSkill
- data-connector-buildingSkill
- declarative-firstSkill
- disk-pressure-forensicsSkill
- early-return-over-elseSkill
- email-triageSkill
- enums-codify-behaviorSkill
- ephemeral-workspace-lifecycleSkill
- event-sourcingSkill
- evidence-claim-boundariesSkill
- exhaustive-matchSkill
- feature-coverage-not-just-line-coverageSkill
- full-disk-forensicsSkill
- gate-before-pushSkill
- github-pr-shepherdingSkill
- graceful-shutdown-stateful-agentsSkill
- grounded-generationSkill
- iac-incident-responseSkill
- iac-not-ad-hocSkill
- instrumented-service-scaffoldSkill
- interface-over-conditionalsSkill
- knowledge-routingSkill
- lean-on-oss-standardsSkill
- live-money-disciplineSkill
- live-state-verificationSkill
- loop-governance-and-learningSkill
- low-level-executor-task-specSkill
- map-dispatch-over-conditionalsSkill
- merge-conflict-disciplineSkill
- mermaid-diagramsSkill
- oke-arc-runners-opentofuSkill
- orchestrate-agySkill
- orchestrate-claudeSkill
- orchestrate-codexSkill
- orchestrate-geminiSkill
- otel-emit-at-willSkill
- parameter-designSkill
- The first 60 shown.
The file
Files
Plugin Authoring
A Claude Code plugin bundles skills (and optionally commands, agents, hooks, MCP servers) into one versioned, installable unit distributed through a marketplace. Getting the structure and manifests right is what makes it install cleanly and pin to a known version — the failure modes are all in the layout and the JSON.
Structure
my-plugin/
.claude-plugin/
plugin.json # the plugin manifest
skills/<name>/SKILL.md
commands/<name>.md # optional
agents/<name>.md # optional
hooks/ # optionalThe marketplace is a separate repo (or root) with a marketplace.json listing
the plugins it offers.
Manifests
plugin.json — identity + version (the thing consumers pin):
{
"name": "my-plugin",
"version": "0.2.0",
"description": "One line on what it provides",
"author": { "name": "...", "email": "..." }
}marketplace.json — the catalog entry pointing at the plugin:
{ "name": "my-marketplace",
"plugins": [{ "name": "my-plugin", "source": "./my-plugin" }] }The loop that prevents broken releases
- Build the structure; keep one capability per skill.
- Validate locally — install the plugin from a local path and confirm the skills/commands actually load before publishing. A manifest that parses but ships a skill that won't load is the classic invisible break.
- Version deliberately — bump
plugin.jsonversionon every change; consumers pin to it, so an unversioned change silently shifts everyone. - Publish by updating the marketplace entry, then have a consumer install the pinned version and verify it resolves.
Discipline
- Version-pin in consumers, never float — reproducibility beats "latest."
- One bundled unit, declared per workload — each workload's config names the plugin + version it gets, so what's installed is auditable.
- Don't ship exec scripts inside skills — keep skills as instructions; put any tooling in the plugin's scripts/commands, audited separately.
Adapted from the MIT-licensed softaworks/agent-toolkit plugin-packaging skill (guidance only; upstream's generator script intentionally omitted).
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.

