Creating a new plugin
Check existing plugins first
Before creating a new plugin, verify that no existing plugin covers your use case. If similar functionality exists, contribute to that plugin instead. See the plugin catalog or browse plugins/ in the repo.
Create a new plugin only when your contribution represents a genuinely distinct capability domain that doesn't fit any existing plugin.
Steps
-
Create a directory under
plugins/with your plugin name (use kebab-case): -
Define
plugin.jsonwith metadata: -
Add commands as Markdown files in
commands/with frontmatter: -
Add skills as
SKILL.mdfiles inskills/<skill-name>/: -
Write a
README.mdthat explains:- What the plugin does
- Prerequisites (tools, tokens, dependencies)
- How to use each command and skill
-
Add evals in
evals/evals.jsonwith at least 2 test cases. See Evaluating skills. -
Test locally:
Reference implementation
Use plugins/hello-world/ as a minimal reference for structure and conventions.