> 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 back to the plugin that ships it.
npx skills add https://github.com/hoangsonww/Claude-Code-Agent-Monitor --skill 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.
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.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take hoangsonww/skill-inventory from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.