Skill

activate-plugin

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.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin claude-vault

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Enable a vault plugin in the current project's `.claude/settings.json`.

SKILL.md

Similar Skills

cache-components

139.3k

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.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars0

Forks0

Last CommitApr 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

activate-plugin

Enable a vault plugin in the current project's .claude/settings.json.

Inputs

The user names a plugin (e.g. "activate the podcast-production plugin"). If ambiguous, run list-vault first or ask.

Steps

Resolve the inventory path per 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.

Resolve the activation key: <plugin-name>@<marketplace-name> from the inventory entry.

Determine project root (cwd or nearest .git/.claude ancestor).

Read <project>/.claude/settings.json. If it doesn't exist, create the directory and start with {}.

Ensure enabledPlugins exists as an object. Set enabledPlugins["<name>@<marketplace>"] = true.

Write the file back with 2-space indentation, preserving any other keys.

Confirm to the user: plugin name, marketplace, settings file path edited, and the reminder that Claude Code must be restarted in this project for the activation to take effect.

Safety

Never edit ~/.claude/settings.json (user-global). This skill is project-scoped only.

If .claude/settings.json already has the plugin enabled, say so and do not rewrite the file.

If the project has a settings.local.json that disables the same plugin, surface the conflict — don't silently override.

Output style

One-line confirmation. Then a single reminder line about restarting Claude Code.

activate-plugin

Enable a vault plugin in the current project's .claude/settings.json.

Inputs

The user names a plugin (e.g. "activate the podcast-production plugin"). If ambiguous, run list-vault first or ask.

Steps

Resolve the inventory path per 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.
Resolve the activation key: <plugin-name>@<marketplace-name> from the inventory entry.
Determine project root (cwd or nearest .git/.claude ancestor).
Read <project>/.claude/settings.json. If it doesn't exist, create the directory and start with {}.
Ensure enabledPlugins exists as an object. Set enabledPlugins["<name>@<marketplace>"] = true.
Write the file back with 2-space indentation, preserving any other keys.
Confirm to the user: plugin name, marketplace, settings file path edited, and the reminder that Claude Code must be restarted in this project for the activation to take effect.

Safety

Never edit ~/.claude/settings.json (user-global). This skill is project-scoped only.
If .claude/settings.json already has the plugin enabled, say so and do not rewrite the file.
If the project has a settings.local.json that disables the same plugin, surface the conflict — don't silently override.

Output style

One-line confirmation. Then a single reminder line about restarting Claude Code.