plugin-forge
Skill0 starsChanged 4 months agoMITView on GitHub
Create and manage Claude Code plugins with proper structure, manifests, and marketplace integration. Use when creating plugins for a marketplace, adding plugin components (commands, agents, hooks), bumping plugin versions, or working with plugin.json/marketplace.json manifests.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Ivan-propio/claude-skillsword for word, first seen Nov 16, 2026
- Samueladewole/claude-skillsword for word, first seen Oct 13, 2026
- aphrody-code/nietheir own version, first seen Sep 23, 2026
- nbirkner/digital-brainword for word, first seen Apr 12, 2026
Other versions4 projects use a version of this.
Word for word · 3
- Ivan-propio/claude-skills★ 0100% same
- nbirkner/digital-brain★ 0100% same
- Samueladewole/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 1
- aphrody-code/nie★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository121 other files it gives its agents.
- agent-md-refactorSkill
- backend-to-frontend-handoff-docsSkill
- c4-architectureSkill
- codexSkill
- command-creatorSkill
- commit-workSkill
- crafting-effective-readmesSkill
- daily-meeting-updateSkill
- database-schema-designerSkill
- datadog-cliSkill
- dependency-updaterSkill
- agency-brand-guardianSkill
- design-system-starterSkill
- agency-ui-designerSkill
- agency-ux-researcherSkill
- difficult-workplace-conversationsSkill
- domain-name-brainstormerSkill
- draw-ioSkill
- agency-ai-data-remediation-engineerSkill
- agency-ai-engineerSkill
- agency-api-platform-engineerSkill
- agency-autonomous-optimization-architectSkill
- agency-backend-architectSkill
- agency-cms-developerSkill
- agency-codebase-onboarding-engineerSkill
- agency-code-reviewerSkill
- agency-database-optimizerSkill
- agency-database-reliability-engineerSkill
- agency-data-engineerSkill
- agency-data-visualization-engineerSkill
- agency-desktop-app-engineerSkill
- agency-devops-automatorSkill
- agency-drupal-performance-engineerSkill
- agency-drupal-shopping-cart-engineerSkill
- agency-email-intelligence-engineerSkill
- agency-embedded-firmware-engineerSkill
- agency-feishu-integration-developerSkill
- agency-filament-optimization-specialistSkill
- agency-finops-engineerSkill
- agency-frontend-developerSkill
- agency-gaussdb-expert-engineerSkill
- agency-git-workflow-masterSkill
- agency-internationalization-engineerSkill
- agency-identity-access-engineerSkill
- agency-incident-response-commanderSkill
- agency-iot-fleet-engineerSkill
- agency-it-service-managerSkill
- agency-llm-post-training-engineerSkill
- agency-minimal-change-engineerSkill
- agency-mobile-app-builderSkill
- agency-mobile-release-engineerSkill
- agency-multi-agent-systems-architectSkill
- agency-network-engineerSkill
- agency-orgscript-engineerSkill
- agency-payments-billing-engineerSkill
- agency-privacy-engineerSkill
- agency-prompt-engineerSkill
- agency-rag-pipeline-engineerSkill
- agency-rapid-prototyperSkill
- agency-realtime-collaboration-engineerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Use create_plugin.py to generate plugin structure:
- Very specific: line 46
Use bump_version.py to update versions in both manifests:
- Distinctive: line 105
Create in respective directories:
- Distinctive: line 191
Important: Update version in BOTH locations:
- Very specific: line 196
Use bump_version.py to automate.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CC Plugin Forge
Purpose
Build and manage Claude Code plugins with correct structure, manifests, and marketplace integration. Includes workflows, automation scripts, and reference docs.
When to Use
- Creating new plugins for a marketplace
- Adding/modifying plugin components (commands, skills, agents, hooks)
- Updating plugin versions
- Working with plugin or marketplace manifests
- Setting up local plugin testing
- Publishing plugins
Getting Started
Create New Plugin
Use create_plugin.py to generate plugin structure:
python scripts/create_plugin.py plugin-name \
--marketplace-root /path/to/marketplace \
--author-name "Your Name" \
--author-email "your.email@example.com" \
--description "Plugin description" \
--keywords "keyword1,keyword2" \
--category "productivity"This automatically:
- Creates plugin directory structure
- Generates
plugin.jsonmanifest - Creates README template
- Updates
marketplace.json
Bump Version
Use bump_version.py to update versions in both manifests:
python scripts/bump_version.py plugin-name major|minor|patch \
--marketplace-root /path/to/marketplaceSemantic versioning:
- major: Breaking changes (1.0.0 → 2.0.0)
- minor: New features, refactoring (1.0.0 → 1.1.0)
- patch: Bug fixes, docs (1.0.0 → 1.0.1)
Development Workflow
1. Create Structure
Manual approach (if not using script):
mkdir -p plugins/plugin-name/.claude-plugin
mkdir -p plugins/plugin-name/commands
mkdir -p plugins/plugin-name/skills2. Plugin Manifest
File: plugins/plugin-name/.claude-plugin/plugin.json
{
"name": "plugin-name",
"version": "0.1.0",
"description": "Plugin description",
"author": {
"name": "Your Name",
"email": "your.email@example.com"
},
"keywords": ["keyword1", "keyword2"]
}3. Register in Marketplace
Update .claude-plugin/marketplace.json:
{
"name": "plugin-name",
"source": "./plugins/plugin-name",
"description": "Plugin description",
"version": "0.1.0",
"keywords": ["keyword1", "keyword2"],
"category": "productivity"
}4. Add Components
Create in respective directories:
| Component | Location | Format |
| Commands | commands/ | Markdown with frontmatter |
| Skills | skills/<name>/ | Directory with SKILL.md |
| Agents | agents/ | Markdown definitions |
| Hooks | hooks/hooks.json | Event handlers |
| MCP Servers | .mcp.json | External integrations |
5. Local Testing
# Add marketplace
/plugin marketplace add /path/to/marketplace-root
# Install plugin
/plugin install plugin-name@marketplace-name
# After changes: reinstall
/plugin uninstall plugin-name@marketplace-name
/plugin install plugin-name@marketplace-namePlugin Patterns
Framework Plugin
For framework-specific guidance (React, Vue, etc.):
plugins/framework-name/
├── .claude-plugin/plugin.json
├── skills/
│ └── framework-name/
│ ├── SKILL.md
│ └── references/
├── commands/
│ └── prime/
│ ├── components.md
│ └── framework.md
└── README.mdUtility Plugin
For tools and commands:
plugins/utility-name/
├── .claude-plugin/plugin.json
├── commands/
│ ├── action1.md
│ └── action2.md
└── README.mdDomain Plugin
For domain-specific knowledge:
plugins/domain-name/
├── .claude-plugin/plugin.json
├── skills/
│ └── domain-name/
│ ├── SKILL.md
│ ├── references/
│ └── scripts/
└── README.mdCommand Naming
Subdirectory-based namespacing with : separator:
commands/namespace/command.md→/namespace:commandcommands/simple.md→/simple
Examples:
commands/prime/vue.md→/prime:vuecommands/docs/generate.md→/docs:generate
Version Management
Important: Update version in BOTH locations:
plugins/<name>/.claude-plugin/plugin.json.claude-plugin/marketplace.json
Use bump_version.py to automate.
Git Commits
Use conventional commits:
git commit -m "feat: add new plugin"
git commit -m "fix: correct plugin manifest"
git commit -m "docs: update plugin README"
git commit -m "feat!: breaking change"Reference Docs
Detailed documentation included:
| Reference | Content |
references/plugin-structure.md | Directory structure, manifest schema, components |
references/marketplace-schema.md | Marketplace format, plugin entries, distribution |
references/workflows.md | Step-by-step workflows, patterns, publishing |
Scripts
| Script | Purpose |
scripts/create_plugin.py | Scaffold new plugin |
scripts/bump_version.py | Update versions |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

