Repo layoutComing soon
Where each file of a plugin goes. The layout matches Claude Code plugins and CoderHelm skill repos.
Coming soon
A plugin is one git repository (or one folder of a marketplace repo) with plugin.yaml at its root.
| Path | What it is |
|---|---|
plugin.yaml | The manifest. Required. See the manifest reference. |
skills/<name>/SKILL.md | Instructions the plugin's agents read, with optional text files next to them. Same format as skills. |
agents/<name>.md | The agents that do the work. The body is the agent's instructions; tools: in the frontmatter lists the tools it uses. |
README.md | For people: what the plugin does and what it needs. Not read by agents. |
The skills and agents fields in the manifest default to skills/*/SKILL.md and agents/*.md. Change them if your files live elsewhere, for example to share a folder with a Claude Code plugin under .claude/.
Limits
The same limits as skill repos apply: up to 200 skills and agents, 64,000 bytes per file, 32,000 bytes per file next to a skill, and 2,000,000 bytes in total.
What doesn't go in the repo
Each team's own values never live in the plugin: brand documents, account ids, keys, approvers. They are settings, filled in by each team when it installs the plugin. That is what lets one public plugin serve many teams.
Build the marketing pluginComing soon
A full walkthrough, from an empty repo to a plugin that drafts launch posts from each release and publishes after an editor approves.
Manifest referenceComing soon
Every field of plugin.yaml, with its type, default and rules. Rendered from the same JSON Schema that the validator uses.