I have reopened the same 60-page PDF multiple times this week, and I still can’t tell you what is in the middle of it. Linear reading has never really clicked for me. Somewhere around page twenty, a long report stops being information and starts being wallpaper. So I built a small Claude skill that takes any document and hands me back a navigable mind map. It’s the same instinct behind turning plain notes into visual maps. A branching picture sticks in my head when paragraphs just slide off it.
I started using Claude instead of these 5 apps — and I’m not going back
The stack got smaller and the work got better
How I talked Claude into building it
It started as one sloppy paragraph, not a plan
I did not sit down with a plan. I opened Claude, described what I wanted in one messy paragraph, and hoped for the best. If you have not used them, Claude skills are reusable instruction sets that teach it to do one job the same way every time, but I did not begin with a skill at all.
The first thing I did was tell Claude, in plain language, what a good mind map looks like to me. Here is roughly what I typed.
I’m going to paste long documents and I want each one turned into a mind map I can actually navigate. Pull out the single main idea, branch the supporting points under it, and keep going a few levels deep. Don’t just copy my headings. Group things by how they actually relate, and give me something interactive I can expand and collapse.
Honestly, the first map was better than I expected. It found the core idea, branched everything sensibly underneath, and the result was interactive, so I could open the parts I cared about and hide the rest.
The catch was that I had to paste those same instructions every single time, and I tweaked the wording on each go, so no two maps came out quite alike — the exact itch a skill is meant to scratch. That is when I asked Claude to lock the whole thing in as a reusable skill, with a few tighter rules baked in.
Save this as a skill called document-mind-map. Whenever I attach a file, read the whole thing first, find the one core idea, then build the hierarchy outward from it. Keep each node to about six words. Flag any link between two branches that isn’t obvious from the headings alone. Render it as a collapsible map, and finish with three questions the document never answers.
That last instruction did more than I expected. The three unanswered questions turn the map into a starting point for actual thinking, not just a prettier table of contents.
- Developer
-
Anthropic PBC
- Price model
-
Free, subscription available
Research papers are where it earns its keep
Map the argument, not the table of contents
The skill works well with most documents, but I find it most handy for research papers. A dense paper has a single argument buried under methodology, citations, and three pages of related work, and most mind-mapping tools just reproduce that structure. I want the opposite.
I tell it to:
Treat the thesis as the center of the map. Everything else should ladder up to that argument, so put the methods and results where they support the claim instead of giving them their own corner.
With that nudge, the map is no longer a summary and becomes a picture of how the paper argues. The first time it worked, it connected two findings I had read as unrelated, and the line between them was the whole point of the paper. I had skimmed right past it twice.
NotebookLM’s mind map feature does something similar with uploaded sources, but I wanted output that follows my rules rather than its own.
Meeting notes and long email threads stop piling up
Decisions and owners, not who said hi
Not everything I feed it is dense or academic. Some of it is just noise I need to get through. A two-week email thread or a page of meeting notes is the kind of thing I usually scroll past and promise to read later and never do.
Skip the small talk. Build the map around decisions, who owns what, and anything still unresolved, and put the deadline on any node that has one.
That turns forty messages of back-and-forth into a map I can read in about ten seconds. The decisions sit at the top, the open questions hang off to one side where I can see them, and the pleasantries disappear, which is exactly where they belong.
My own rough drafts get an X-ray
If a branch is empty, the structure is broken
The use I did not see coming was turning the skill on my own work. Before I write a piece, I sketch a rough outline, and I now run that outline through the skill before I write a real sentence. I use the following prompt:
This is my own outline, not a finished piece. Map it exactly as written without smoothing anything over, so I can see where a section is thin or a branch has nothing under it.
A healthy outline makes a balanced map. A broken one makes a lopsided one, with a fat branch on the left and a lonely node on the right that has nothing under it. That lonely node is almost always the section I have not yet thought through.
It has also helped me hold onto more of what I read. There is solid evidence that turning what you read into a mind map helps you retain it, and I have felt that with manuals and course material I would otherwise forget by the weekend.
It is not magic, and I still read the source
The map flattens nuance, so I verify what matters
I lean on this skill almost every day, but I do not trust it unquestioningly. A mind map is a compression of a document, and you know, compression loses things. It can tidy a careful, hedged argument into something cleaner and more confident than the author ever intended.
So I still open the source for anything that matters, especially numbers, dates, and any claim I plan to repeat out loud. The map tells me where to look. It does not do the looking for me.
It also needs something to work with. If I feed it a rambling, unstructured brain dump, the map comes out just as scattered because it can only organize what is already there.
I added one line to my Claude prompts and stopped getting generic answers
One question from Claude was worth more than ten better prompts from me
Reaching for a map is now the habit, not the exception
Lowering the effort mattered more than finding a new tool
The part that stuck with me is not any single map. It is how little effort it now takes. When something costs you one step, you stop rationing it, and you run documents through it that you’d once have skimmed and forgotten. Now I take a real look at a report I would otherwise have half-read.
That also lines up with where these tools are going. Claude can build interactive visuals right inside a conversation, so the distance between reading something and seeing it laid out keeps shrinking. Understanding a document used to mean grinding through it. Lately, it means looking at it first.
