Stats
Actions
Tags
How this skill is triggered — by the user, by Claude, or both
Slash command
/plugin-dev:usageThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Dev tool for syncing Claude Code plugin cache from local sources.
Dev tool for syncing Claude Code plugin cache from local sources.
!"${CLAUDE_PLUGIN_ROOT}/scripts/plugin-dev" version 2>&1 || echo "(plugin-dev not available)"
!"${CLAUDE_PLUGIN_ROOT}/scripts/plugin-dev" status 2>&1 || echo "(could not get status)"
plugin-dev status — shows which plugins are staleplugin-dev sync <name> — partial name match (e.g. plugin-dev sync meta)plugin-dev sync --all/reload-plugins is not sufficient)For repos not registered as a known marketplace:
$PWD/.claude-plugin/marketplace.json exists, plugin-dev uses it automaticallyplugin-dev --source /path/to/repo sync --allRun /plugin-dev:install to add plugin-dev to your PATH.
On Windows, run /plugin-dev:update after plugin updates to re-copy the script.
| Path | Purpose |
|---|---|
~/.claude/plugins/cache/ | Plugin cache (what plugin-dev syncs) |
~/.claude/plugins/installed_plugins.json | Installed plugin registry |
~/.claude/plugins/known_marketplaces.json | Marketplace sources |
npx claudepluginhub bengous/claude-code-plugins --plugin plugin-devManages third-party Claude Code plugin updates: force immediate updates via empty arg or view status dashboard with 'status'. Auto-runs on session start.
Troubleshoots Claude Code plugin registry issues like installation scopes, orphaned entries, project-scoped visibility bugs, and debugging failures. Details structure of ~/.claude/plugins/installed_plugins.json.
Provides quick reference for Claude Code plugins: structure, manifest, installation commands, marketplaces, management UI, and standalone vs plugins comparison.