Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add thoreinstein/gemini-obsidian --skill cross-linker -a claude-code
Open on GitHub

What 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/ and reference/, 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-code

2Manually: put the files in place

~/.claude/skills/cross-linker/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/cross-linker/

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.

cross-linker Ar9av cross-linker finds wiki pages that ought to reference each other but don't, then inserts the missing [[wikilinks]]. Useful right after a bulk import of notes. CX Codex +1 3,300installs obsidian-kb-artifacts Galaxy-Dawn obsidian-kb-artifacts — a skill for Obsidian formatting and derived artifacts: wikilinks, registry tables, canvas files, Bases, and link repair. Works in Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. CX Codex +1 328installs obsidian-markdown davila7 obsidian-markdown is a Claude Code skill for creating and editing Obsidian Markdown notes. It activates for .md work in Obsidian and requests about wikilinks, callouts, or note properties. CX Codex +1 490installs obsidian-skills kepano Teaches the agent to work with Obsidian files: Markdown with wikilinks, embeds and callouts, Bases for database views, and Canvas for visual diagrams. ★ 3,785repo stars llm-wiki Ar9av llm-wiki is a Claude Code skill that defines a personal Obsidian wiki's source layers, categories, project trees and page template. It applies when deciding how knowledge should be stored. CX Codex +1 4,200installs wiki-query Ar9av wiki-query searches and synthesizes answers from a compiled Obsidian vault using graph indexing without modifying existing notes. CX Codex +1 3,600installs second-brain NicholasSpisak second-brain scaffolds a personal note repository in Obsidian designed around an LLM wiki architecture. A five-step wizard configures vault paths, agent rules, and optional CLI utilities. CX Codex +1 2,900installs

From the same set15

The whole set →
research research is a Claude Code skill that searches an Obsidian vault, reads relevant notes, and follows links to answer questions about stored knowledge. CX Codex +1 ★ 102repo stars moc-update moc-update finds the Maps of Content (MOCs) in an Obsidian vault that should link to a freshly created Engineering/ note. Fires on prompts like “update MOC” or “which MOCs”. CX Codex +1 ★ 102repo stars link-audit link-audit audits Obsidian vaults for broken wikilinks and orphaned notes. Helps repair target paths or generate new links via semantic search. CX Codex +1 ★ 102repo stars knowledge This skill finds ideas repeated across project notes and drafts a shared note in Engineering/. Use it to turn recurring project knowledge into a linked concept. CX Codex +1 ★ 102repo stars journal journal — a skill for your Obsidian daily note: it reads today's entry, appends quick logs and builds weekly or end-of-day reviews from CLI sessions. CX Codex +1 ★ 102repo stars obsidian-companion obsidian-companion connects your assistant to an Obsidian vault to edit files, inspect broken wikilinks, and run queries using local RAG. CX Codex +1 ★ 102repo stars vault-lint vault-lint audits an Obsidian vault across five checks and returns a prioritised report with fixes you accept one at a time. CX Codex +1 ★ 102repo stars wiki-ingest wiki-ingest distills external files, transcripts, and Readwise exports into structured Obsidian notes with RAG-based deduplication and source tracking. CX Codex +1 ★ 102repo stars

Project sponsors

Companies that keep this analytics open