inventorylisted

Enumerate the complete Claude Code ECOSYSTEM this machine can invoke. Every built-in CLI command with its aliases and hidden/gated status, every bundled skill, and every component of every installed plugin (skills, agents, commands, hooks, MCP servers, LSP servers, workflows, output styles, themes, monitors, bin) across all marketplaces. Reads the shipped binary because the official docs publish no built-in command list. Reports; never changes anything. Use when: 'what slash commands do I have', 'list all my skills', 'what agents are available', 'show me every plugin component', 'what does Claude Code ship built-in', 'is /foo a real command', 'what changed after the update', 'show me only the plugin ones', 'what does marketplace X give me'. Not for: auditing the install DIRECTORY on disk (use /claude-ops:audit-install-state), updating or converging the plugin fleet (use /claude-ops:plugins), or checking settings and permission drift (use /claude-config:audit).
melodic-software/claude-code-plugins · ★ 13 · AI & Automation · score 73

Install: claude install-skill melodic-software/claude-code-plugins

## Purpose Answers one question completely: **what can this machine actually invoke, and where did each thing come from?** That question has no single documented answer. Claude Code's own documentation does not publish a list of its built-in slash commands. `docs/en/slash-commands` now serves the skills page, because commands were merged into skills, so the only complete source for the built-in surface is the shipped executable. Plugin components, by contrast, are on disk and enumerable directly. This skill reads both and keeps them clearly separated, because they are evidence of different quality. The report is an inventory, not a judgement. Nothing here says a component is stale, misconfigured, or wrong; the neighbours below own those verdicts. ## Scope boundary | Question | Owner | |---|---| | What can I invoke, and where did it come from? | **this skill** | | Is my install directory healthy. What is stale, what does the product manage? | `/claude-ops:audit-install-state` | | Is the plugin fleet current, and at what scope? | `/claude-ops:plugins audit` | | Are settings, hooks, permissions, and MCP config correct? | `/claude-config:audit` | | Which permission scopes hold which rules? | `/claude-config:audit-permission-state` | The distinction that matters most: `audit-install-state` inventories **files on disk**, this skill inventories **capabilities that resolve**. A plugin can be present on disk and contribute nothing because it is disabled, and a built-in command c