public-plugin-builder

Guides users through a 23-step workflow to design, generate, and publish Claude plugins to GitHub.

3.4k|487|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/davepoon/buildwithclaude --skill public-plugin-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: public-plugin-builder
Source: https://github.com/davepoon/buildwithclaude/tree/main/plugins/public-plugin-builder/skills/public-plugin-builder
Command: npx skills add https://github.com/davepoon/buildwithclaude --skill public-plugin-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building a Claude plugin requires knowing many undocumented conventions: SKILL.md frontmatter, plugin.json and marketplace.json schemas, skills/ versus agents/ folder routing, and marketplace validation rules. This Skill walks users from a raw idea to a fully deployed plugin without missing any structural requirement.

Core Features & Use Cases

  • Phased Interview Process: Runs a 23-step guided workflow across discovery, design, classification, generation, and push phases, confirming each decision before proceeding.
  • Plugin Type Classification: Automatically classifies the idea as a Skill, Skill-with-scripts, Agent, or Commands based on computation needs and slash-command requirements.
  • Complete File Generation: Produces SKILL.md, plugin.json, marketplace.json, README.md, Python scripts, and LICENSE following validated schema rules.
  • Use Case: A developer says "help me make a plugin that scores startup pitches." The Skill interviews them about inputs and outputs, researches open-source libraries, generates all plugin files, and pushes them to a GitHub repo ready for marketplace installation.

Quick Start

Ask the assistant to help you build a new Claude plugin from your idea and answer its step-by-step questions.

Frequently Asked Questions about public-plugin-builder

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

FAQPage Schema
How do I build a Claude Code plugin from scratch?

Start by defining the problem, target users, inputs, and outputs through a structured interview. Then classify the plugin type, generate SKILL.md, plugin.json, and marketplace.json files, and push everything to a GitHub repository for installation.

What is the difference between skills and agents in Claude plugins?

Skills live in the skills/ folder and support explicit slash-command triggers like /plugin:name, with optional Python scripts. Agents live in agents/ and are auto-triggered by Claude based on intent only, with no slash-command access.

Can a Claude plugin work on both claude.ai and Claude Code?

Yes, pure reasoning skills without Python scripts work on both platforms. Plugins requiring Python computation, file system access, or git operations only work on Claude Code, so the builder may generate dual skill-plus-agent versions.

Why does my Claude plugin fail marketplace validation?

Common causes include missing owner or plugins fields in marketplace.json, using author email instead of url, adding unsupported skills or agents arrays to plugin.json, or using a marketplace name containing restricted words like claude or anthropic.

When should plugin knowledge go in SKILL.md versus separate files?

Taxonomies, rubrics, templates, and schemas should be embedded directly in the SKILL.md prompt body rather than separate reference files. This prevents knowledge drift and keeps extractable documentation close to the reasoning logic.