Scan, classify, and visualize all skills in the workspace. Produces an interactive HTML report with two views — a layered dependency graph and a structured analysis panel showing routing conflicts, layer violations, duplicate capabilities, missing abstractions, and a prioritized action plan. Use when the user wants to audit skill organization, reduce routing errors, understand skill dependencies, or plan a skill consolidation. Trigger on: skill map, skill graph, skill audit, skill organization, routing optimization, skill overlap, skill layers, skill dependencies.
Scan all skills in the workspace, classify them into layers, map dependencies, run a routing/efficiency analysis, and produce an interactive HTML report.
Skills live in multiple locations. Scan all of:
| Location | Pattern |
|---|---|
| Root skills | skills/*/SKILL.md |
| Workspace skills | workspaces/*/skills/*/SKILL.md |
| Nested sub-skills | skills/*/*/SKILL.md (recursive) |
| Project/product skills | workspaces/*/products/*/SKILL.md, workspaces/*/*/SKILL.md |
For each SKILL.md found, extract from frontmatter:
name, descriptionworkspaces/<ws>/ → ws name; otherwise root)From the body, extract:
scripts/ sibling dir)Skip: _shared/, references/, files starting with _, archive dirs.
Assign every skill to one of three layers:
| Layer | Name | What belongs here |
|---|---|---|
| L0 | Infrastructure & Connectors | Connects to external systems. Provides generic capability. No business logic. Examples: browser automation, SSH, DB query engine, email SMTP, file storage, MCP bridge, media processing, secret management |
| L1 | Domain Knowledge & Data | Encodes business rules, metrics definitions, calibration standards, query templates for a specific domain. Retrieves/transforms domain data. Does not orchestrate multi-step workflows |
| L2 | Task & Workflow Orchestration | Runs an end-to-end workflow. Coordinates multiple steps, sub-agents, or other skills. Produces a final deliverable (report, published page, PR, audit, campaign) |
Classification heuristics:
For each skill, record:
Valid dependency directions: L2 → L1 → L0 and L2 → L0. Flag any upward dependency (lower layer calling higher) as a violation.
Compute all six analysis dimensions below. Be systematic — check every skill pair for conflicts, every skill for violations.
Two skills conflict when the same user phrase could reasonably trigger either. Detection signals:
For each conflict: