CC Plugin Forge: scaffold and manage Claude Code plugins

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://github.com/softaworks/agent-toolkit/blob/main/dist/plugins/plugin-forge/skills/plugin-forge/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.