Skill

activate-bundle

Apply a named bundle from the Claude Vault inventory — activates all plugins and MCP servers the bundle declares in the current project. Use when the user names a bundle ("activate the podcast bundle").

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

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Apply a bundle: a named set of plugins + MCP servers defined in the inventory. Equivalent to running `activate-plugin` and `activate-mcp` for each member, but in one shot.

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 30, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

activate-bundle

Apply a bundle: a named set of plugins + MCP servers defined in the inventory. Equivalent to running activate-plugin and activate-mcp for each member, but in one shot.

Inputs

The user names a bundle (e.g. "activate the podcast bundle"). If ambiguous, run list-vault filtered to bundles.

Steps

Resolve and read the inventory per skills/_shared/inventory-path.md. Find bundles[] entry by name. If not found, tell the user and stop — suggest list-vault.

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

Validate before mutating: for each entry in the bundle's plugins and mcpServers, confirm the referenced item still exists in the inventory's top-level plugins / mcpServers arrays. Collect missing references.

If any references are missing, surface them and ask whether to proceed with the rest or abort. Do not silently skip.

For each plugin in the bundle: apply the same logic as activate-plugin (set enabledPlugins["<name>@<marketplace>"] = true in .claude/settings.json). Skip ones already active, count them.

For each MCP server in the bundle: apply the same logic as activate-mcp (write to .mcp.json, add to enabledMcpjsonServers). Skip ones already mounted with matching config; ask before overwriting on config mismatch.

Aggregate any env vars referenced by activated MCP configs (${VAR} placeholders) and list them once at the end.

Single restart reminder for the whole batch.

Safety

Project-scoped only.

Atomic-ish: if step 3 finds missing references and the user aborts, write nothing.

Never apply a bundle to user-global settings.

Output style

Per-member status line (activated / already active / skipped). Totals line. Env-vars-needed line if applicable. One restart reminder.

activate-bundle

Apply a bundle: a named set of plugins + MCP servers defined in the inventory. Equivalent to running activate-plugin and activate-mcp for each member, but in one shot.

Inputs

The user names a bundle (e.g. "activate the podcast bundle"). If ambiguous, run list-vault filtered to bundles.

Steps

Resolve and read the inventory per skills/_shared/inventory-path.md. Find bundles[] entry by name. If not found, tell the user and stop — suggest list-vault.
Determine project root (cwd or nearest .git/.claude ancestor).
Validate before mutating: for each entry in the bundle's plugins and mcpServers, confirm the referenced item still exists in the inventory's top-level plugins / mcpServers arrays. Collect missing references.
If any references are missing, surface them and ask whether to proceed with the rest or abort. Do not silently skip.
For each plugin in the bundle: apply the same logic as activate-plugin (set enabledPlugins["<name>@<marketplace>"] = true in .claude/settings.json). Skip ones already active, count them.
For each MCP server in the bundle: apply the same logic as activate-mcp (write to .mcp.json, add to enabledMcpjsonServers). Skip ones already mounted with matching config; ask before overwriting on config mismatch.
Aggregate any env vars referenced by activated MCP configs (${VAR} placeholders) and list them once at the end.
Single restart reminder for the whole batch.

Safety

Project-scoped only.
Atomic-ish: if step 3 finds missing references and the user aborts, write nothing.
Never apply a bundle to user-global settings.

Output style

Per-member status line (activated / already active / skipped). Totals line. Env-vars-needed line if applicable. One restart reminder.