Skill

list-active

Show which vault plugins and MCP servers are currently active in the current project. Use when the user asks "what's enabled here", "what's active in this project", or wants to audit the project's tool surface before activating more.

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

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Inspect the current project's Claude Code configuration and report what's enabled.

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.

list-active

Inspect the current project's Claude Code configuration and report what's enabled.

Steps

Determine the project root — the current working directory, or walk up to the nearest directory containing .claude/ or .git/.

Read these files if they exist (treat missing as empty):

<project>/.claude/settings.json — look at enabledPlugins (object: "name@marketplace": true) and enabledMcpjsonServers (array of MCP server names from .mcp.json).
<project>/.claude/settings.local.json — same shape, may override.
<project>/.mcp.json — mcpServers object (name → config).

Resolve the inventory path per skills/_shared/inventory-path.md and read it (treat missing as empty). Label each active item as vault (present in inventory) or external (not in inventory).

Render:

Active plugins — name, marketplace, source (vault/external)
Active MCP servers — name, source (vault/external), enabled-state (in .mcp.json AND in enabledMcpjsonServers, or only in .mcp.json)
If nothing is active, say so explicitly — don't render empty headings.

Note any settings.local.json overrides separately so the user sees them.

Output style

Compact. One line per entry. Mark vault items with [vault], external with [ext]. End with totals.

list-active

Inspect the current project's Claude Code configuration and report what's enabled.

Steps

Determine the project root — the current working directory, or walk up to the nearest directory containing .claude/ or .git/.
Read these files if they exist (treat missing as empty):
- <project>/.claude/settings.json — look at enabledPlugins (object: "name@marketplace": true) and enabledMcpjsonServers (array of MCP server names from .mcp.json).
- <project>/.claude/settings.local.json — same shape, may override.
- <project>/.mcp.json — mcpServers object (name → config).
Resolve the inventory path per skills/_shared/inventory-path.md and read it (treat missing as empty). Label each active item as vault (present in inventory) or external (not in inventory).
Render:
- Active plugins — name, marketplace, source (vault/external)
- Active MCP servers — name, source (vault/external), enabled-state (in .mcp.json AND in enabledMcpjsonServers, or only in .mcp.json)
- If nothing is active, say so explicitly — don't render empty headings.
Note any settings.local.json overrides separately so the user sees them.

Output style

Compact. One line per entry. Mark vault items with [vault], external with [ext]. End with totals.