Skill Vision v1.1.0 — see the codebase, not just the verdict
A sixth tool, alongside the five validators: skill_mapper.py draws a skill's files and reference graph as a Mermaid flowchart, instead of a score.
Why: progressive disclosure means Claude starts at SKILL.md and follows links outward. A file nothing links to is never read, however well it's written — that's a shape problem, and a picture answers it faster than a findings list.
What's new
scripts/skill_mapper.py— Mermaid flowchart (TD/LR/BT/RL), grouped by directory.--detailadds each script's function/class counts and CLI flags read straight off its AST.--jsonfor the graph as data. No call-graph inference: published recall for static Python call graphs tops out around 70%, so this tool draws only what's checkable againstlsandgrep— files and resolved links, nothing guessed.- Same resolver as the spec check, on purpose.
spec_validator.py's link-checking logic is nowbuild_graph(), a shared function both tools call. The map and the CONFORMANT/NOT CONFORMANT verdict use the same graph, so they can't drift apart. - 131 tests (up from 117), including a parity suite asserting the mapper and the spec validator report the same broken and orphaned files on the same skill.
- Writes no file by default, only Mermaid to stdout — pipe it yourself:
python3 scripts/skill_mapper.py path/to/skill --fence > diagram.md.
Install / upgrade
git clone https://github.com/AlveeeRahman/skill-vision.git ~/.claude/skills/skill-vision
# or, for an existing clone:
git -C ~/.claude/skills/skill-vision pull