list-components

Discover installed Claude Code components and their provenance via a Ruby script.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/rwc9u/claude-config --skill list-components-rwc9u
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: list-components
Source: https://github.com/rwc9u/claude-config/tree/main/skills/list-components
Command: npx skills add https://github.com/rwc9u/claude-config --skill list-components-rwc9u

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The skill eliminates manual, error-prone inspection of a Claude Code setup by automatically discovering all installed components and showing where each item originates, saving time during audits, onboarding, and debugging.

Core Features & Use Cases

  • Comprehensive discovery: Enumerates installed plugins, standalone skills, user commands, agents, hooks, MCP servers, and LSP servers.
  • Source attribution: Identifies marketplace origins, local-directory installs, symlinks, local files, and plugin-bundled components.
  • Audit and troubleshooting: Useful for security audits, migration planning, resolving extension conflicts, and documenting an environment's provenance.

Quick Start

Run the discovery script to generate a detailed, source-attributed inventory of installed skills, commands, agents, hooks, MCP servers, and LSP servers.

Frequently Asked Questions about list-components

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inventory installed Claude Code plugins, skills, and hooks?

To inventory installed Claude Code plugins, skills, and hooks, run a Ruby discovery script that parses plugin registries and manifest files to output a source-attributed list of all components. It resolves symlinks and SKILL.md frontmatter for accurate provenance.

What is the best way to audit MCP and LSP servers in a Claude Code setup?

Auditing MCP and LSP servers in Claude Code is best handled by a discovery script that enumerates all installed components and identifies their origins. It attributes sources like marketplaces, local directories, or plugin bundles for security reviews.

Does Claude Code component discovery require any external dependencies or gems?

Claude Code component discovery requires no external dependencies or gems. The Ruby discovery script operates entirely using the Ruby standard library, parsing manifest files and resolving symlinks without needing additional package installations.

How do I resolve symlink provenance for Claude Code skills and commands?

To resolve symlink provenance for Claude Code skills and commands, the discovery script traces symlink targets and parses SKILL.md frontmatter. It identifies whether components originate from local directories, marketplaces, or plugin bundles.

Can I check where my Claude Code agents and user commands are installed from?

You can check where Claude Code agents and user commands are installed from by running an inventory script that provides source attribution. It maps each component to its origin, distinguishing between marketplace installs, local files, and plugin-bundled items.