Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | 63% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -43% | 0% |
| case-08 | ✗→✓ | ▲ Improved | -63% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 0% | 0% |
| case-10 | ✗→✓ | ▲ Improved | -56% | 0% |
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.
The user provides: $ARGUMENTS
This may be:
name matches.| 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 } }] } |
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.
From /plugins, list each plugin with enabled state and its contributes.skills count. Note that /skills reports only the user's own skill dirs — plugin skills are counted via contributes, so reconcile: total available skills ≈ user skills + Σ enabled-plugin contributes.skills.
Flag where a plugin name or a plugin's contributed-skill domain overlaps with a user-authored skill of the same name or purpose (compare against frontmatter.description from /skills). Recommend keeping one source of truth — prefer the plugin version if it is maintained upstream, or the user version if it is customized.
Flag plugins with enabled: false (their skills are inert) and any whose installPathExists is false (manifest references a missing install) — these are dead weight to clean up via the Claude Code plugin manager.
Scope | Name | Size | Description).Plugin | Enabled | Skills | Agents | Commands).Claude Code plugin commands, not this dashboard.
http://localhost:4820, say so and tellthe user to start it with npm start from the repo root.
Other measured skills in the registry, with their headline benchmark lift.