plugin-development
Guide plugin development workflows with validation, disable strategies, and error handling. Use when working on plugin development, plugin system changes, or plugin options validation.
Best use case
plugin-development is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Guide plugin development workflows with validation, disable strategies, and error handling. Use when working on plugin development, plugin system changes, or plugin options validation.
Teams using plugin-development should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/plugin-development/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How plugin-development Compares
| Feature / Agent | plugin-development | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Guide plugin development workflows with validation, disable strategies, and error handling. Use when working on plugin development, plugin system changes, or plugin options validation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Plugin Development ## Rule Anchor - `AGENTS.md` > "Development Patterns" - `AGENTS.md` > "Rules and Skills Boundary" ## Scope Use this skill for designing or updating plugins in the project plugin system. ## Preconditions - A plugin base type exists (e.g., a BasePlugin abstraction). - Plugin options are validated at construction time. - Error handling uses the project-standard plugin error type. ## Workflow 1. **Define plugin identity** - Set a stable name and version. 2. **Validate options early** - Validate constructor options and strategy flags. - Return actionable errors with context. 3. **Provide disable controls** - Support `enabled: false`. - Support `strategy: 'silent'` or `strategy: 'none'`. 4. **Implement core behavior** - Keep behavior deterministic and configurable. 5. **Document usage** - Add usage examples and configuration notes. ## Checklist - [ ] Name and version are defined. - [ ] Options validation runs in the constructor. - [ ] Disable controls are available and tested. - [ ] Error messages include context and actionable guidance. - [ ] Configuration examples are documented. ## References - Plugin guide: `packages/agents/docs/PLUGINS.md`