skill-inventory

1# Skill Inventory
2 
3Map every skill available to the user — both their own (user/project scope) and
4the ones contributed by installed plugins — read through the Agent Monitor
5dashboard at `http://localhost:4820`.
6 
7## Input
8 
9The user provides: **$ARGUMENTS**
10 
11This may be:
12- empty — inventory all skills (default).
13- a skill name fragment — focus on skills whose `name` matches.
14- a plugin name — show only the skills that plugin contributes.
15 
16## Data Sources
17 
18| Endpoint | Returns |
19|----------|---------|
20| `GET /api/cc-config/skills` | `{ items:[{ scope:"user"\|"project", name, path, file, size, mtime, frontmatter, preview }] }` — the user's own skill directories |
21| `GET /api/cc-config/plugins` | `{ manifestPath, manifestExists, plugins:[{ key, name, marketplace, scope, version, enabled, installPath, contributes:{ skills, agents, commands, outputStyles, hooks } }] }` |
22 
23## Report Sections
24 
25### 1. User & project skills
26From `/skills`, list each skill with `scope`, `name`, `size` (KB), and
27`frontmatter.description` (or the start of `preview`). Separate user-scope from
28project-scope skills.
29 
30### 2. Plugin-contributed skills
31From `/plugins`, list each plugin with `enabled` state and its
32`contributes.skills` count. Note that `/skills` reports only the user's own
33skill dirs — plugin skills are counted via `contributes`, so reconcile: total
34available skills ≈ user skills + Σ enabled-plugin `contributes.skills`.
35 
36### 3. Overlap & duplication
37…