plugin-builder

Build, test, debug, and distribute plugins for Claude Code and Cowork.

1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/fercosnt/fernando-claude-marketplace --skill plugin-builder-fercosnt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-builder
Source: https://github.com/fercosnt/fernando-claude-marketplace/tree/main/skills/plugin-builder
Command: npx skills add https://github.com/fercosnt/fernando-claude-marketplace --skill plugin-builder-fercosnt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Creating plugins for Claude Code and Cowork involves many subtle rules — manifest placement, hook auto-discovery, path portability, sandbox constraints — and violating any of them causes silent, hard-to-debug failures. This Skill guides the full plugin lifecycle so plugins load, trigger, and distribute correctly. ## Core Features & Use Cases - End-to-end plugin workflow: Six phases covering planning, scaffolding, component building (skills, commands, hooks, agents, MCP), local testing, debugging, and distribution via marketplace, GitHub, or npm. - Component specifications: Detailed references for SKILL.md frontmatter rules, command syntax, hook events, MCP transports, and agent definitions, plus Cowork-specific sandbox and connector guidance. - Debugging and validation: Systematic fixes for common failures (skills not triggering, duplicate hooks, hardcoded paths) plus a pre-release validation checklist. - Use Case: You have a standalone skill in ~/.claude/skills/ and want to ship it to your team on Cowork — this Skill walks you through porting it, adapting language for non-developers, packaging as a .plugin file, and publishing. ## Quick Start Ask Claude to scaffold a new plugin with one skill for your chosen workflow, then follow the guided phases to test, debug, and distribute it.

Frequently Asked Questions about plugin-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a plugin for Claude Code?

Create a directory with .claude-plugin/plugin.json containing name, version, description, and author, then add components like skills/, commands/, or hooks/ at the plugin root. Test locally with claude --plugin-dir or a dev marketplace, then restart Claude Code after installing.

Why is my plugin skill not triggering?

Skills usually fail to trigger because the description is vague or missing explicit trigger phrases. Verify the SKILL.md sits in skills/ at the plugin root (not inside .claude-plugin/), uses only documented frontmatter fields, and lists all phrasings users might say.

Can I use the same plugin in Claude Code and Cowork?

Yes, both share the same plugin system, but Cowork runs in a VM sandbox that blocks private APIs, Docker, git credentials, and build steps. Use MCP servers and connectors for external tools, and keep everything as Markdown, JSON, and pre-built scripts.

What causes the duplicate hooks error in a plugin?

The error occurs when hooks/hooks.json is referenced inside plugin.json. The hooks.json file is auto-discovered by convention, so remove the reference from the manifest and the error disappears.

How do I distribute a Claude plugin to my team?

Options include GitHub direct (/plugin marketplace add org/repo), the official marketplace submission, npm registries, or team settings via extraKnownMarketplaces. For Cowork, package the plugin as a .plugin zip file after running claude plugin validate.