From claude-vault
Disable a plugin in the current project by removing its entry from .claude/settings.json enabledPlugins. Symmetric counterpart to activate-plugin.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin claude-vaultThis skill uses the workspace's default tool permissions.
Remove a plugin's activation from the current project's `.claude/settings.json`. The plugin stays installed — only the project-level enable flag is removed.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Remove a plugin's activation from the current project's .claude/settings.json. The plugin stays installed — only the project-level enable flag is removed.
The user names a plugin. If ambiguous, run list-active first.
.git/.claude ancestor).<project>/.claude/settings.json. If missing or enabledPlugins is empty, tell the user nothing's active and stop.enabledPlugins. The user may give just the plugin name (e.g. podcast-production) or the full activation key (podcast-production@danielrosehill). Match on either.false (explicitly disabled rather than enabled), surface that and ask whether to remove the entry entirely or leave the disable in place.enabledPlugins becomes empty after removal, leave it as {} rather than deleting the key — keeps the schema stable.settings.local.json too: warn if the plugin is enabled there independently (deactivation in settings.json won't override that).One-line confirmation. Restart reminder.