Skill

list-vault

List plugins, MCP servers, and bundles available in the user's Claude Vault inventory. Use when the user asks what's in their vault, what they could activate, or "show me my vault".

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

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Read the vault inventory and present its contents grouped by category.

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-vault

Read the vault inventory and present its contents grouped by category.

Steps

Resolve the inventory path per skills/_shared/inventory-path.md (the canonical resolver: $CLAUDE_USER_DATA → $XDG_DATA_HOME/claude-plugins → ~/.local/share/claude-plugins, then /claude-vault/inventory.json). Read it. If it doesn't exist, tell the user the resolved path and point at the README format, then stop. Do not fall back to ~/.claude/.

Parse the JSON. Expected top-level keys: plugins (array), mcpServers (array), bundles (array). Any may be missing — treat as empty.

Render a compact summary:

Plugins — name, marketplace, description, tags
MCP Servers — name, description, tags
Bundles — name, description, what it activates

If the user asked for a filter (by tag, by name pattern, by category), apply it before rendering.

Output style

Group by category with a heading per group. One line per entry. Skip empty groups. End with totals: N plugins, M MCP servers, K bundles.

Do not echo the raw JSON unless the user asks.

list-vault

Read the vault inventory and present its contents grouped by category.

Steps

Resolve the inventory path per skills/_shared/inventory-path.md (the canonical resolver: $CLAUDE_USER_DATA → $XDG_DATA_HOME/claude-plugins → ~/.local/share/claude-plugins, then /claude-vault/inventory.json). Read it. If it doesn't exist, tell the user the resolved path and point at the README format, then stop. Do not fall back to ~/.claude/.
Parse the JSON. Expected top-level keys: plugins (array), mcpServers (array), bundles (array). Any may be missing — treat as empty.
Render a compact summary:
- Plugins — name, marketplace, description, tags
- MCP Servers — name, description, tags
- Bundles — name, description, what it activates
If the user asked for a filter (by tag, by name pattern, by category), apply it before rendering.

Output style

Group by category with a heading per group. One line per entry. Skip empty groups. End with totals: N plugins, M MCP servers, K bundles.

Do not echo the raw JSON unless the user asks.