From vault-mind
Use when the user wants to find non-obvious connections between their existing notes, e.g. "what connects to my Koopman operator note", "find links I'm missing in my philosophy of mind notes", "connect my ML and chemistry notes". Surfaces conceptual overlaps that aren't wikilinked yet and suggests where THEY might draw the link. May insert a wikilink they approve; never writes note prose.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vault-mind:connectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A Zettelkasten pays off through its links. This skill finds conceptual overlaps between
A Zettelkasten pays off through its links. This skill finds conceptual overlaps between notes the user has already written that aren't yet connected, and shows them where a link belongs, so they make the connection (and the understanding that comes with it). You find candidate links; they decide and learn from them.
Core rule: never author note prose. Inserting a wikilink into the links key or fixing a link is a metadata/structure edit and is fine with their approval. Writing explanatory sentences in a note body is not; that's theirs.
Read the vault profile (.vault-mind/profile.md) first if you haven't this session (paths +
frontmatter schema; run /vault-mind:init if missing). "Notes dir", "links key", "tags key"
below refer to the profile's values.
connect X): read note X, its links/wikilinks, and notes that share
its tags. That's the candidate pool.connect my philosophy of mind notes): gather notes by tag/name match.connect my ML and chemistry notes): pull both clusters; the goal is
bridges between them.# from the vault root; substitute the profile's dir/key names:
rg -l 'tag-or-term' <notes_dir> # candidate notes
rg -o '\[\[[^]]+\]\]' "<notes_dir>/X.md" # existing links out of X
For each candidate pair, judge: do these share a mechanism, structure, method, or idea , and is that link not already present (not in either note's links key or body)?
Prioritize:
/vault-mind:gaps signal).Skip links that are already there or are trivial/restating the tag.
Give 3–8 suggested connections, strongest first. For each:
[[Note A]] ↔ [[Note B]]: the specific shared idea, in one or two lines.Also call out orphans and dead links separately.
If they say yes to specific links, you may edit metadata/structure:
[[Note B]] to Note A's links key (and vice-versa), preserving frontmatter order.Do not add prose to note bodies explaining the connection; that's the part they write to actually learn it. Confirm what you changed.
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.
npx claudepluginhub jeff7712/vault-mind --plugin vault-mind