skill-inventory
Inventory the installed skills and which plugins contribute them, then flag overlap with the user's own skills — read through the Agent Monitor Config Explorer API. Reads /api/cc-config/skills and /api/cc-config/plugins. Use when managing skills: deduping, deciding what to keep, or tracing a skill back to the plugin that ships it.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill skill-inventory --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Skill Inventory Map every skill available to the user — both their own (user/project scope) and the ones contributed by installed plugins — read through the Agent Monitor dashboard at `http://localhost:4820`. ## Input The user provides: **$ARGUMENTS** This may be: - empty — inventory all skills (default). - a skill name fragment — focus on skills whose `name` matches. - a plugin name — show only the skills that plugin contributes. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/cc-config/skills` | `{ items:[{ scope:"user"\|"project", name, path, file, size, mtime, frontmatter, preview }] }` — the user's own skill directories | | `GET /api/cc-config/plugins` | `{ manifestPath, manifestExists, plugins:[{ key, name, marketplace, scope, version, enabled, installPath, contributes:{ skills, agents, commands, outputStyles, hooks } }] }` | ## Report Sections ### 1. User & project skills From `/skills`, list each skill with `scope`, `name`, `size` (KB), and `frontmatter.description` (or the start of `preview`). Separate user-scope from project-scope skills. ### 2. Plugin-contributed skills From `/plugins`, list each plugin with `enabled` state and its `contribute
- Input
- Data Sources
- Report Sections
- 1. User & project skills
- 2. Plugin-contributed skills
- 3. Overlap & duplication
- 4. Disabled / orphaned plugins
- Output
What does the skill-inventory skill do?
Inventory the installed skills and which plugins contribute them, then flag overlap with the user's own skills — read through the Agent Monitor Config Explorer API. Reads /api/cc-config/skills and /api/cc-config/plugins. Use when managing skills: deduping, deciding what to keep, or tracing a skill back to the plugin that ships it.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill skill-inventory --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.