菜单
Scaffold a new plugin inside an existing marketplace — the shipped dir skeleton, plugin.json, install.sh with the Git-Bash guard, settings.json, and CLAUDE.md; then register it in the catalog and in release-please packages with the catalog extra-files sync. Use when adding a plugin to a marketplace.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit a marketplace (or a single plugin) — run the shipping-hygiene sensor, structural checks (every catalog entry has a dir, every dir has a manifest, versions in sync), and the portability sweep. Reports findings and offers fixes. Use to validate a marketplace is healthy.
Generate the gated SessionStart install hook plus cloud-setup.sh and a "use skills directly" fallback so the marketplace is usable in Claude Code web/cloud sessions. Use to make a marketplace cloud-aware.
Scaffold a new Claude Code plugin-marketplace monorepo — catalog, repo-root tests/scripts/docs trees, CI workflows, release-please config, dev-setup, the hygiene sensor, and a root CLAUDE.md. Use when starting a fresh marketplace repository.
Run shellcheck -x over every shipped and dev shell script, flag bash-4/GNU-only constructs, verify env-bash shebangs, and check that each install.sh has the Git-Bash-on-Windows guard. Use to validate cross-platform portability (macOS bash 3.2 / BSD / Windows Git Bash).
Wire release-please with one package per plugin and the marketplace.json extra-files jsonpath sync, so plugin.json, the release tag, and the catalog entry can never drift. Use to set up or repair automated versioning + catalog sync.
| name | add-plugin |
| description | Scaffold a new plugin inside an existing marketplace — the shipped dir skeleton, plugin.json, install.sh with the Git-Bash guard, settings.json, and CLAUDE.md; then register it in the catalog and in release-please packages with the catalog extra-files sync. Use when adding a plugin to a marketplace. |
| user-invocable | true |
<name> [description]Add a new shipped plugin to the current marketplace and wire its release/catalog sync.
Read ${CLAUDE_PLUGIN_ROOT}/knowledge/marketplace-conventions.md (§2, §6).
Confirm .claude-plugin/marketplace.json exists (run /new-marketplace first if
not). Find the repo url from the root CLAUDE.md or ask the user.
Shipped dir skeleton. Create plugins/<name>/ with .claude-plugin/,
skills/, commands/, agents/, hooks/, knowledge/, templates/. Only
create the subdirs the plugin will actually use; never create a tests/ dir
inside the plugin.
Manifest. Copy ${CLAUDE_PLUGIN_ROOT}/templates/plugin/plugin.json to
plugins/<name>/.claude-plugin/plugin.json; fill __NAME__,
__DESCRIPTION__, __OWNER_NAME__. Version starts at 0.1.0.
install.sh. Copy ${CLAUDE_PLUGIN_ROOT}/templates/plugin/install.sh (it
includes the Windows/Git-Bash guard); replace __NAME__; chmod +x. Add any
plugin-specific need <tool> checks.
settings.json + CLAUDE.md. Copy the templates from
${CLAUDE_PLUGIN_ROOT}/templates/plugin/. If the plugin has no hooks, you may
omit settings.json. Document the plugin's commands in its CLAUDE.md.
Register in the catalog. Append an entry to
.claude-plugin/marketplace.json .plugins:
{
"name": "<name>",
"version": "0.1.0",
"description": "<description>",
"source": {
"source": "git-subdir",
"url": "<repo-url>",
"path": "plugins/<name>",
"ref": "<name>-v0.1.0"
}
}
Use jq to edit so the JSON stays valid.
Register the release package. Add the per-plugin block from
${CLAUDE_PLUGIN_ROOT}/templates/release/release-please-config.json (with
__NAME__ replaced) into release-please-config.json .packages, and add
"plugins/<name>": "0.1.0" to .release-please-manifest.json. This wires the
extra-files catalog sync so version + ref can never drift.
Verify + report. Run bash scripts/ci-local.sh (or at minimum
bash scripts/structural-check.sh and bats tests/repo). Report the new
files and the green gate.
Refuse to place any test/build script inside plugins/<name>/; if the plugin
needs tests, put them under repo-root tests/<name>/.