cross-linker · thoreinstein — Claude Code skill for finding missing links
cross-linker finds mentions of other Obsidian notes that lack wikilinks, then sorts possible links by confidence. Use it to connect notes across a chosen folder or a wider vault scope.
ISC ★ 102 updated 2026-10-25
npx skills add thoreinstein/gemini-obsidian --skill cross-linker -a claude-codeWhat cross-linker does
The skill builds a registry of notes from their titles, aliases, paths, and types, then scans note text for mentions of other pages. It ignores existing wikilinks, code, frontmatter, and a note’s own heading. Findings are grouped by source note and ranked by confidence.
Exact title matches in Pattern, Trap, or Decision notes can be linked automatically. Medium-confidence matches need confirmation; low-confidence suggestions are listed for review. The skill links only the first unlinked mention of each target in a source note. Short titles such as “Testing” can produce noisy matches.
The default scope is Engineering/. Pass another folder as an argument, or use --deep to include working/ and reference/. The workflow uses Obsidian tools such as obsidian_list_notes and obsidian_replace_in_note.
What it helps with
- find note mentions that lack wikilinks
- add links to concepts in a selected folder
- rank proposed links by confidence
- spot missing connections between vault notes
Example prompts for the agent
- Find missing links in
Engineering/Patterns/with/cross-linker Engineering/Patterns/. - Scan more of the vault, including
working/andreference/, with/cross-linker --deep. - Find unlinked mentions across
Engineering/and show me the report.
How to install cross-linker
1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill cross-linker -a claude-code2Manually: put the files in place
~/.claude/skills/cross-linker/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cross-linker/
1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill cross-linker -a codex2Manually: put the files in place
.agents/skills/cross-linker/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill cross-linker -a cursor2Manually: put the files in place
.cursor/skills/cross-linker/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install thoreinstein/gemini-obsidian skills/cross-linker2Manually: put the files in place
.github/skills/cross-linker/SKILL.md1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill cross-linker -a gemini-cli2Platform CLI
gemini skills install https://github.com/thoreinstein/gemini-obsidian --path skills/cross-linkerManually: put the files in place
.devin/skills/cross-linker/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cross-linker
How do I install cross-linker in Claude Code?
Run npx skills add thoreinstein/gemini-obsidian --skill cross-linker -a claude-code. The skill file is at ~/.claude/skills/cross-linker/SKILL.md.
What does cross-linker do?
It finds mentions of other Obsidian pages that are not wikilinks, ranks the matches, and proposes links. It can apply exact matches automatically; medium-confidence suggestions require confirmation.
What scope does cross-linker scan by default?
It scans Engineering/ by default. Pass a folder path to choose another scope, or use --deep to include working/ and reference/.
Source text
SKILL.md · ISC
---
name: cross-linker
description: >-
Use when the user wants to find and insert missing wikilinks across vault
notes. Triggers on "cross-link", "find missing links", "weave links",
"unlinked mentions", "add wikilinks", or "link notes together".
---
# Cross-Linker
Discover unlinked mentions of vault concepts and insert `[[wikilinks]]`. Complements `link-audit` (which finds broken/orphan links) by finding links that *should exist but don't*.
## Workflow
### Phase 1 — Build Page Registry
1. Call `obsidian_list_notes` on the target scope (default: `Engineering/`).
2. For each note, call `obsidian_read_note` and extract from frontmatter:
- **Title** (from `# heading` or filename)
- **Aliases** (from `aliases:` frontmatter field, if present)
- **Type** (pattern, trap, decision, concept)
3. Build a registry: `{ title, aliases[], path, type }` for each note.
For large scopes (>50 notes), batch reads and process incrementally.
### Phase 2 — Scan for Unlinked Mentions
For each note in scope:
1. Call `obsidian_read_note` to get the full body text.
2. For each *other* page in the registry, check if the page's title or any alias appears in the body text **without** being wrapped in `[[...]]`.
3. Skip matches inside:
- Existing wikilinks `[[...]]`
- Code blocks (fenced or inline)
- Frontmatter
- The note's own title/heading
4. Record each match: `{ source_note, target_note, matched_text, line_context, confidence }`
### Phase 3 — Score and Rank
Assign confidence to each proposed link:
- **High** — exact title match (case-insensitive), target is a Pattern/Trap/Decision note
- **Medium** — alias match, or title match in a less structured note
- **Low** — partial match or only semantically related (use `obsidian_rag_query` to verify)
Sort findings: high confidence first, grouped by source note.
### Phase 4 — Present Findings
Show the user a report:
```
## Cross-Link Report for: Engineering/
### High Confidence (auto-apply)
- Engineering/Patterns/table-driven-tests.md
Line 12: "table driven tests" → [[Table-Driven Tests]]
### Medium Confidence (confirm each)
- Engineering/Traps/mock-drift.md
Line 8: "interface injection" → [[Interface Injection]]
### Low Confidence (review)
- working/appiary/knowledge/auth.md
Line 23: "token" → possibly [[Token Rotation]] ?
### Summary
- X high-confidence links ready to apply
- Y medium-confidence links for review
- Z low-confidence suggestions
```
### Phase 5 — Apply Links
- **High confidence:** Apply automatically using `obsidian_replace_in_note`, replacing the first unlinked mention with `[[Target Title]]` or `[[path/to/note|display text]]`.
- **Medium confidence:** Apply one at a time, asking user to confirm each.
- **Low confidence:** List for reference only — don't auto-apply.
Only link the **first** unlinked mention of each target per source note. Repeated mentions stay as plain text (standard wiki convention).
## Arguments
- Optional scope: `/cross-linker Engineering/Patterns/` (default: `Engineering/`)
- Optional depth: `/cross-linker --deep` to include `working/` and `reference/` scopes
## Tips
- Run on a narrow scope first (`Engineering/Patterns/`) to calibrate before going vault-wide
- If a note has many false positives, it may need `aliases:` in frontmatter to disambiguate
- Short titles (1-2 words like "Testing" or "Auth") generate noise — prefer linking specific concept names
- After running, consider `/link-audit` to verify no broken links were introduced
© thoreinstein · ISC · thoreinstein/gemini-obsidian
Similar skills
All skills for Notes, tasks and projects →cross-linker by other authors comes first.