md-to-map
Skill2 starsChanged yesterdayMITView on GitHub
Convert existing Markdown notes (.md files or a whole folder of them) into interactive mind maps, using a script so the notes are never read into context. Use when the user types /md-to-map, or asks to turn notes, docs, plans, ideas or old .md files into a mind map, import notes into the mind map, or "map out this file".
In this repository17 other files it gives its agents.
- autopilotSkill
- autopsySkill
- confidence-mapSkill
- delegateSkill
- expert-askSkill
- failure-museumSkill
- ghost-usersSkill
- grill-dumpSkill
- intent-diffSkill
- mind-mapSkill
- premortemSkill
- red-teamSkill
- shipitSkill
- stuck-detectorSkill
- taste-thiefSkill
- tournamentSkill
- workSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Use this for existing notes.
- Very specific: line 14
Run from the user's project folder (maps are written under ./mindmaps/):
- Very specific: line 27
If a file produced 0–1 nodes (prose with no headings or bullets): tell the user, and offer to run /mind-map <slug> so it can be structured …
- Very specific: line 29
Avoid: reading or summarizing the notes, overwriting an existing map, editing generated map-data.js by hand.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
MD → Mind Map
Requires the mind-map skill installed next to this one. If ${CLAUDE_SKILL_DIR}/../mind-map/scripts/import.mjs is missing, stop and tell the user to install mind-map first. Don't improvise a converter.
Use this for existing notes. For a fresh idea with no notes, use /mind-map instead.
- Get the path of a
.mdfile or folder from the user. If none is given, ask. Don't read the files yourself: the script parses them for free. - Run from the user's project folder (maps are written under
./mindmaps/):
node ${CLAUDE_SKILL_DIR}/../mind-map/scripts/import.mjs <file.md | folder> [--out mindmaps]- One map per file, at
mindmaps/<slug>/. A folder is searched recursively. - An existing map is skipped, never overwritten.
- Mapping rules:
#→ title, deeper headings → branches, nested bullets → sub-branches, leaf bullets → details,Look:/Feel:/Does:→ lenses,- [ ]→ open questions,>→ quotes, first paragraph → core/summary. Code blocks and tables are ignored.
- Reply with the script's output lines as they are, plus one line:
Open: <dir>/index.html in a browser · continue with /mind-map <slug>
If a file produced 0–1 nodes (prose with no headings or bullets): tell the user, and offer to run /mind-map <slug> so it can be structured by asking questions. Don't restructure it yourself unless they ask.
Avoid: reading or summarizing the notes, overwriting an existing map, editing generated map-data.js by hand.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

