10 Commands That Make My Obsidian Vault Think
Originally published on Medium. Read here free — no account needed.
For two years my second brain was a very tidy filing cabinet. Two thousand markdown notes in Obsidian, all sorted with PARA, all searchable, and mostly just sitting there.
The notes weren’t the problem. The problem was that using them still took manual effort. Finding a connection, remembering when I first had an idea, pressure-testing a belief before a decision, all of it meant me doing the digging. Storage went up and leverage stayed flat.
So I stopped trying to organize my way out of it and started building commands instead. Each one is a custom slash command in Claude Code pointed at my vault, and each one does something I used to do by hand. Ten commands later, the vault doesn’t just hold my thinking, it thinks with me. 🧠
If you’ve read my earlier post on wiring Claude Code into Obsidian, this is the sequel: less about setup, more about the specific commands that earned a permanent spot. Here are the ten I actually run.
1. /sync: Load Your Whole Context in One Shot
Description: Reads recent weekly notes, active projects, the master task list, and everything modified in the last 7 days, then hands back a structured summary of where I actually am.
What it does:
- Scans _Weekly/ for the last few reviews
- Walks every active folder in 1. Projects/
- Pulls the master task list and recent inbox items
- Outputs current projects, priorities, and focus areas
Why it earns its spot: Every new Claude session used to start with me re-explaining my life. Now I type /sync and it tells me what I'm in the middle of. It's the command I run first, every session, and it makes all the others sharper because they're working from real context.
2. /trace [topic]: The Timeline of an Idea
Description: Tracks how a single idea has evolved across the vault. It finds every mention, follows the wikilinks, and builds a chronological timeline from first appearance to current state.
What it does:
- Searches all notes for the topic
- Orders the hits by date
- Shows when the idea first showed up, how it shifted, and what it’s connected to now
Why it earns its spot: I ran /trace Skill-Based Engineering and watched a throwaway line in a weekly note turn into a project, then a blog pillar, over four months. You can't see that arc by scrolling. Ideas don't arrive finished, and this is the only way I've found to actually watch one grow up.
3. /connect [topic A] and [topic B]: Find the Bridge
Description: Finds connections between two domains using the vault’s wikilink graph. It surfaces the notes that already bridge the topics and the patterns in how they relate.
What it does:
- Maps the link neighborhood around both topics
- Finds notes that touch both
- Names the pattern connecting them, not just the overlap
Why it earns its spot: This is where the vault stops being a search engine and starts being a collaborator. /connect PARA method and AI agents pointed me at a note I'd forgotten, and that overlap became the outline for a whole article. Run it with no arguments and it scans the entire vault for unlinked-but-related notes, which is a small thrill every time.
4. /ghost [question]: Answers in My Own Voice
Description: Answers a question the way I would, based on my writing style and stated beliefs across the vault. It studies my voice, my reasoning patterns, and my values, then drafts a response that actually sounds like me.
What it does:
- Analyzes tone and argument structure from my own notes
- Pulls my documented positions on the topic
- Drafts an answer in first person, citing the notes it drew from
Why it earns its spot: When I’m stuck on what I think, /ghost reflects my own reasoning back at me and I can react to it. It's a mirror, so it's only as good as what I've written down, but that's the point. It makes me want to write more down.
5. /challenge [topic]: Pressure-Test Before You Commit
Description: Argues with me. It reviews everything I’ve written on a topic and hunts for contradictions, weak points, hidden assumptions, and the perspectives I quietly skipped.
What it does:
- Gathers all notes on the belief or decision
- Flags internal conflicts and logical gaps
- Surfaces the counter-argument I’ve been avoiding
Why it earns its spot: I run this before any decision that’s hard to reverse. It caught me assuming a side project had demand I’d never actually validated. A second brain that only agrees with you is just a bigger echo chamber, and /challenge is the antidote.
6. /ideas: Surface the Patterns You're Too Close to See
Description: Scans the vault for emerging patterns and generates an ideas report of tools to build, people to reach out to, topics to investigate, and things to write. All grounded in my actual activity, not generic brainstorming.
What it does:
- Reads across recent notes and projects for repeated themes
- Clusters them into concrete, actionable suggestions
- Ties each idea back to the notes that sparked it
Why it earns its spot: Half my blog calendar came out of /ideas. When you're inside your own vault every day, the patterns are invisible. This steps back far enough to say "you keep circling this, maybe write it." 💡
7. /backlinks [cluster]: Repair the Graph
Description: Analyzes the link graph to find orphan notes, missing connections, and cluster bridges, then scores each recommendation and hands back a tiered report with specific edits to make.
What it does:
- Finds notes with no inbound links
- Spots pairs that should be linked but aren’t
- Ranks fixes by conceptual strength and structural impact
Why it earns its spot: An orphan note is a thought you’ll never find again. /backlinks is basically a maintenance crew for the part of PKM everyone neglects, and it gives you a punch list instead of a vague "you should link more." Point it at one cluster (/backlinks OMS_Athena) when you don't want the whole vault at once.
8. /graduate [weeks]: Rescue Half-Formed Ideas
Description: Scans weekly notes for undeveloped thoughts and promotes them into standalone seedling notes, each with the core claim, its context, the original excerpt, and connections.
What it does:
- Reads the last few weeks of weekly notes
- Spots the one-liners that deserve to be real notes
- Writes them out to 0. Inbox/Graduates/ as proper seedlings
Why it earns its spot: My best ideas were dying as throwaway bullets in Friday reviews. /graduate catches them before they scroll off into the archive forever. It turned "consistency beats topic selection" from a buried aside into a note I actually built on.
9. /inbox: Auto-Sort Into PARA
Description: Processes everything in 0. Inbox/ and files it into the right PARA folder, judging each note's relevance against my existing structure.
What it does:
- Reads each inbox item’s content
- Picks the right Projects/Areas/Resources home
- Routes multi-topic notes to Resources and links them from the relevant projects
Why it earns its spot: The inbox is where second brains go to die. A pile of unsorted captures is a pile of guilt. /inbox clears it in one pass and, crucially, files things where I'll actually stumble on them again. This one I've even wired to run on a nightly schedule.
10. /money [domain]: The Revenue Advisor Living in My Notes
Description: Acts as a strategic revenue advisor. It mines the vault for assets, skills, relationships, and credibility signals, diagnoses my revenue system first, then recommends prioritized opportunities and the artifacts to build right now.
What it does:
- Inventories what I’ve already got that’s sellable
- Diagnoses the system (recurring vs. one-time, pricing, product vs. service)
- Ranks opportunities by effort-to-revenue and offers to draft the rate card or pitch
Why it earns its spot: This is the command that surprised me most. My vault knows more about my sellable skills than I do in the moment, and /money reads them back as a plan. It's the difference between notes as a diary and notes as an asset.
The Real Shift
Look at that list and you’ll notice none of these commands store anything. They act. /trace reads time, /challenge reads for weakness, /money reads for leverage. The notes were always there. The commands are what turned them into thinking.
The catch is that every one of these is only as good as what you’ve fed the vault. /ghost can't sound like you if you've never written like you. /challenge can't find your blind spots if you never wrote down the belief. The commands reward the writing habit. The more you put in, the sharper the vault gets.
You don’t need all ten to start. Build /sync and /trace first, live with them for a week, and you'll feel the shift from storage to leverage fast enough that the other eight write themselves.
All ten live in my Staksmith repo on GitHub, where you can read the actual skill definitions and lift the ones you want for your own vault.
Which one would you build first?