- Home
- Skills
- Outfitter Dev
- Agents
- Plugin Engineer
plugin-engineer_skill
- TypeScript
25
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill outfitter-dev/agents --skill plugin-engineer- SKILL.md6.8 KB
Overview
This skill transforms external repositories—CLIs, libraries, MCP servers—into Claude Code plugins with actionable skills and components. It guides the end-to-end pipeline from discovery and repo reconnaissance through pattern extraction, component authoring, packaging, and audit. Use it to convert real-world codebases into well-structured, distributable plugins.
How this skill works
The skill sequences discrete stages: discovery of external docs and community patterns, internal recon of the target repo, pattern extraction, mapping patterns to component types, authoring components, packaging as a plugin, and delegating an audit. Each stage uses specialized outfitter helper skills (research, codebase-recon, patterns, codify, skills-dev, claude-plugins, claude-plugin-audit) and stores artifacts under artifacts/plugin-engineer/. Quick mode short-circuits stages for simple, single-purpose repos.
When to use it
- Turning a CLI tool into a Claude Code plugin
- Creating skills that wrap an external library or API
- Building plugin companions for MCP servers
- Extracting repeatable automation patterns from a third-party repo
- Packaging workflow patterns around external tools
Best practices
- Always start with discovery and track outputs in artifacts/plugin-engineer/
- Validate that a pattern has at least three realistic use cases before authoring a component
- Prefer skills for multi-step workflows and commands for quick single actions
- Use the provided outfitter authoring skills rather than reinventing component scaffolding
- Run a formal audit before packaging or publishing the plugin
Example use cases
- Convert a developer CLI into a plugin exposing common commands as quick commands and a guided skill
- Wrap an HTTP library into skills that perform authenticated calls and parse responses
- Create a plugin companion for an MCP server to manage deployments and status checks
- Automate frequent multi-step workflows found in a repo (e.g., build→test→publish) by extracting and codifying patterns
- Quick-mode: package a small single-purpose CLI into a 1–2 skill plugin for immediate distribution
FAQ
Use Quick Mode for small repos with under five primary commands or a clear single purpose; it skips pattern extraction and mapping to speed delivery.
What artifacts are produced and where?
Artifacts live in artifacts/plugin-engineer/: discovery.md, recon.md, patterns.md, mapping.md, components/, and audit.md to track progress and decisions.
Do I need custom agents for most plugins?
No. Only introduce agents for complex orchestration needs; most plugins are best implemented as skills and commands.