CC Plugin Forge: scaffold and manage Claude Code plugins
Create plugins with correct structure, plugin.json/marketplace.json manifests, components, versioning, local testing and publishing workflows
- What
- Create plugins with correct structure, plugin.json/marketplace.json manifests, components, versioning, local testing and publishing workflows
- Cost
- Free
- Needs
- Claude Code (or a compatible plugin host); Python 3 to run the scaffolding scripts; a marketplace root to publish into
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @softaworks's CC Plugin Forge: build and manage Claude Code plugins with correct structure, manifests and marketplace integration. Create a new plugin with create_plugin.py (scaffolds the directory structure, generates the plugin.json manifest, a README template, and registers it in marketplace.json); add components (commands with subdirectory-based namespace:command naming, skills, agents, hooks, MCP servers); bump versions in both manifests with bump_version.py (semantic versioning); test locally (/plugin marketplace add, install, uninstall, reinstall); and publish. Includes framework/utility/domain plugin patterns, a manual structure fallback, a version-management checklist, conventional-commit guidance, and bundled reference docs (plugin-structure.md, marketplace-schema.md, workflows.md). Honest caveats: the skill ships its own automation scripts (create_plugin.py, bump_version.py) — review them before running; covers plugin manifests and mechanics, not marketplace approval or distribution processes. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
CC Plugin Forge is a free Muse skill for building and managing Claude Code plugins with correct structure, manifests and marketplace integration. Its create_plugin.py scaffolds the directory structure, generates the plugin.json manifest and a README template, and registers the plugin in marketplace.json, while components use subdirectory-based namespace and command naming.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 3027f20Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Claude Code (or a compatible plugin host); Python 3 to run the scaffolding scripts; a marketplace root to publish into Install "CC Plugin Forge: scaffold and manage Claude Code plugins" for me. It gives my agent @softaworks's plugin-forge workflow: scaffold a new plugin with create_plugin.py (structure, plugin.json manifest, README, marketplace.json registration), add components (commands with namespace:command naming, skills, agents, hooks, MCP servers), bump versions in both manifests with bump_version.py, test locally via /plugin marketplace add/install/uninstall, and publish — with framework/utility/domain patterns and reference docs. MIT-licensed. Repository: https://raw.githubusercontent.com/softaworks/agent-toolkit/3027f20f3181758385a1bb8c022d4041dfb4de84/dist/plugins/plugin-forge/skills/plugin-forge/SKILL.md Pinned version: install the code at commit 3027f20f3181758385a1bb8c022d4041dfb4de84 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "plugin-forge". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. review create_plugin.py and bump_version.py before running them; point the agent at my marketplace root). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 3027f20 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.