← Back

Skills mapping

A dynamic node map of my Claude skills library, which I designed and built with AI: what each skill does, when it loads, and where two skills overlap.

About the tool

Tool · Built with AI · AI skills
Why
A library of AI skills grows fast. Past a few dozen, nobody can see which ones load every session, which load only at a certain build step, and where two skills claim the same ground and give mixed advice.
Built by me
I designed and built the map myself, using AI (Claude Code) to write the code and work through the skills library.
What it does
Reads the skills library and the project's build plan, then draws every skill as a node, linked to what it depends on and to the build step it belongs to.
Status at a glance
Each skill is marked available, missing or excluded, and always-on or conditional, so you can see what Claude will actually load.
Overlaps
Highlights skills that cover the same ground. Both load and their advice is merged with no clear winner, which at this scale is the failure that matters.
Three views
Radial for where each skill lives, Phase board for what it's for, and Flow for how skills connect to the always-on rules, the build plan and Claude Code itself.
Findings
A list of what needs fixing, each with how it was found, such as looking on disk, asking git or reading a document. They copy out as a list to discuss.
The relationship engine
Built on the same evidenced relationship engine as DanceMapz. Every link between two skills is a claim with evidence behind it, such as a file found on disk, a git record or a document that says so, and the map shows how each one was established. It surfaces three kinds of gap: missing links, links with no evidence, and links you'd expect but nobody has recorded.
Used for
Build plans, front-end design and code review, and keeping the library tidy as it grows.

Screens

Get in touch

Looking for a product and UX/UI designer for a contract role? I'd like to hear about it.

Start a conversation