skills/skill-visualizer/SKILL.md
Generate interactive HTML visualizations of the skills collection, codebase structure, or dependency graphs. Uses D3.js for interactive visualization with collapsible nodes, color-coded categories, and hover details. Triggers on "visualize skills", "generate skill map", "codebase visualization", or "show skill dependencies".
npx skillsauth add mhylle/claude-skills-collection skill-visualizerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate interactive HTML visualizations for exploring skills, codebase structure, and dependencies.
This skill creates browser-viewable HTML files with interactive diagrams. It supports multiple visualization types and outputs self-contained HTML files that open directly in any browser.
$0: Output type - skills, codebase, or deps (default: skills)Examples:
/skill-visualizer - Generate skills collection map/skill-visualizer skills - Generate skills collection map/skill-visualizer codebase - Generate codebase structure visualization/skill-visualizer deps - Generate skill dependency graphskills)Generates an interactive force-directed graph of all skills showing:
codebase)Generates a treemap visualization of the project structure:
deps)Generates a directed graph showing skill dependencies:
# Run directly
python ~/.claude/skills/skill-visualizer/scripts/visualize.py skills
# Output location
docs/visualizations/skills-map-YYYY-MM-DD.html
All visualizations are saved to docs/visualizations/:
skills-map-YYYY-MM-DD.htmlcodebase-structure-YYYY-MM-DD.htmlskill-deps-YYYY-MM-DD.htmlThe skill uses Python scripts in scripts/ directory:
visualize.py - Main visualization generatortesting
One-command issue-to-merge pipeline orchestrator. Drives a GitHub issue through nine stages (preflight, plan, implement, review, ci, cloud_review, deploy, e2e, logs) with two human gates, persisting all run state to files so a crashed or interrupted run resumes losslessly. Triggers on "/ship-issue" with an issue number or URL. User-invoked only.
tools
--- name: tt-workflow-build description: Tasktracker-native trigger for a PARALLEL build via the Claude Code Workflow tool. Thin by design — it does two things, then drives to done: (1) ensure a tasktracker project exists (use the existing one, or create one), then (2) start a dynamic `Workflow` that builds it, tracking the work in tasktracker and using the build + verify skills. It does NOT analyze parallelism up front, ask the user to choose a mode, hand back, or fall back to a sequential skil
tools
--- name: grumpy-reviewer description: A single grumpy, nitpicky structural code reviewer that runs as an isolated subagent and treats the code as third-party work submitted by a junior programmer for validation. It cares about exactly one thing — maintainability — judged through separation of concerns, service-oriented design, helper-method extraction, small files, and the rule of 7 (as any grouping nears 7 members, it pushes for sub-groupings). It is deliberately kept OUT of the implementation
development
--- name: tt-workflow-run description: Tasktracker-native autonomous build-loop orchestrator. Drives a first-class `workflow_run` end-to-end — create the run (Gate 1 lifecycle completeness + Gate 2 zero-defects-in), then loop while `getNextReadyTask(projectId)` returns a slice — `setActiveTask` → record a pre-slice `scanArchitectureDrift` baseline → delegate the slice to `/tt-implement-phase` (which does the code work, registers the architecture delta in-slice, and auto-logs defects/learnings/fr