Stats
Actions
Tags
From claude-vault
Enable a plugin from the Claude Vault inventory in the current project by editing the project's .claude/settings.json. Use when the user wants to "activate", "turn on", or "enable" a vault plugin for the current repo only.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-vault:activate-pluginThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Enable a vault plugin in the current project's `.claude/settings.json`.
Enable a vault plugin in the current project's .claude/settings.json.
The user names a plugin (e.g. "activate the podcast-production plugin"). If ambiguous, run list-vault first or ask.
skills/_shared/inventory-path.md and read it. Find the plugin entry by name. If not found, tell the user and stop — suggest list-vault.<plugin-name>@<marketplace-name> from the inventory entry..git/.claude ancestor).<project>/.claude/settings.json. If it doesn't exist, create the directory and start with {}.enabledPlugins exists as an object. Set enabledPlugins["<name>@<marketplace>"] = true.~/.claude/settings.json (user-global). This skill is project-scoped only..claude/settings.json already has the plugin enabled, say so and do not rewrite the file.settings.local.json that disables the same plugin, surface the conflict — don't silently override.One-line confirmation. Then a single reminder line about restarting Claude Code.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin claude-vaultCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.