cross-linker
Scan the Obsidian wiki and automatically discover missing cross-references between pages. Use this skill when the user says "link my pages", "find missing links", "cross-reference", "connect my wiki", "add wikilinks", "what pages should be linked", or after any large ingestion to ensure new pages are woven into the existing knowledge graph. Also trigger when the user mentions "orphan pages" in the context of wanting to connect them, or says things like "my wiki feels disconnected" or "pages aren't linked well". This is a write-heavy skill — it actually modifies pages to add links, unlike wiki-lint which just reports issues.
Ar9av · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Ar9av/obsidian-wiki --skill cross-linker技能说明
name: cross-linker description: > Scan the Obsidian wiki and automatically discover missing cross-references between pages. Use this skill when the user says "link my pages", "find missing links", "cross-reference", "connect my wiki", "add wikilinks", "what pages should be linked", or after any large ingestion to ensure new pages are woven into the existing knowledge graph. Also trigger when the user mentions "orphan pages" in the context of wanting to connect them, or says things like "my wiki feels disconnected" or "pages aren't linked well". This is a write-heavy skill — it actually modifies pages to add links, unlike wiki-lint which just reports issues.
Cross-Linker — Automated Wiki Cross-Referencing
You are weaving the wiki's knowledge graph tighter by finding and inserting missing [[wikilinks]] between pages that should reference each other but currently don't.
Follow the Retrieval Primitives table in llm-wiki/SKILL.md. Build the registry in Step 1 by grepping frontmatter only (not full pages). Reserve full Read for the unlinked-mention detection pass, and even there, only read pages whose summaries/titles make them plausible link targets. Blind full-vault reads are what this framework exists to avoid.
Before You Start
Writing profile: Before drafting or rewriting natural-language Markdown, read and apply the Writing Profile Resolution section in llm-wiki/SKILL.md. Framework schema, provenance, safety, and operation-specific requirements take precedence.
WRITING.md preferences apply only to newly drafted or rewritten natural-language Markdown; preserve source content and structured records.
- Resolve config — follow the Config Resolution Protocol in
llm-wiki/SKILL.md(inline@nameoverride → walk up CWD for.env→ global config → prompt setup). This givesOBSIDIAN_VAULT_PATHandOBSIDIAN_LINK_FORMAT(default:wikilink). - Read
index.mdto get the full inventory of pages and their one-line descriptions - Skim
log.mdto see what was recently ingested (focus linking effort on new pages)
When inserting links in Step 4, apply the link format from llm-wiki/SKILL.md (Link Format section) using the OBSIDIAN_LINK_FORMAT value. When OBSIDIAN_LINK_FORMAT=markdown, compute the relative .md path from the file being edited to the target page.
Step 1: Build the Page Registry
Glob all .md files in the vault (excluding _archives/, _readouts/, .obsidian/). For each page, extract:
- Filename (without
.md) — this is the wikilink target - Title from frontmatter
- Aliases from frontmatter (if any)
- Tags from frontmatter
- Category from frontmatter or directory inference
- One-line summary — first sentence or
titlefield
Build a lookup table:
page_name → { path, title, aliases, tags, summary }
This is your "vocabulary" — every entry in this table is a valid wikilink target.
Step 2: Scan for Missing Links
For each page in the vault:
-
Read the full content
-
Extract existing wikilinks — find all
[[...]]references already present -
Search for unlinked mentions — check if the page's text contains any of these, without being wrapped in
[[...]]:- Page filenames (e.g., the word "MyProject" appears but
[[projects/my-project/my-project]]is missing) - Page titles from frontmatter
- Aliases from frontmatter
- Entity names, project names, concept names from the registry
- Page filenames (e.g., the word "MyProject" appears but
-
Check for semantic connections — pages that share multiple tags or are in the same project directory but don't link to each other
Matching Rules
- Case-insensitive matching for names (e.g., "my-project" matches page
MyProject) - Diacritic-insensitive matching — normalize both the page name and the body text with Unicode NFKD (decompose accented characters to base + combining marks, strip combining marks) before comparing. This ensures body text "Muller" matches page
[[entities/müller]]and vice versa. - Skip self-references — a page shouldn't link to itself
- Skip common words — don't link "the", "and", generic terms. Only match on distinctive names
- Prefer the shortest unambiguous wikilink path — use
[[page-name]]not[[full/path/to/page-name]]when the name is unique across the vault - Don't link inside code blocks or frontmatter
- Don't double-link — if
[[foo]]already appears on the page, don't add another
Step 3: Score and Rank Suggestions
Not every possible link is worth adding. Score each candidate using a composite signal, then tag it with a confidence label.
Scoring
| Signal | Points | Example |
|---|---|---|
| Exact name match in text | +4 | "MyProject" appears in body text → link to my-project.md |
| Shared tags (2+) | +2 | Both tagged #ai #agent but no link between them |
| Same project, no link | +2 | Both under projects/my-project/ but don't reference each other |
| Mentioned entity/concept | +2 | Page mentions "knowledge graphs" → link to [[concepts/knowledge-graphs]] |
| Cross-category connection | +2 | Source is in concepts/, target is in entities/ (or skills/ ↔ synthesis/) — different knowledge layers make this link more architecturally valuable |
| Peripheral→hub reach | +2 | Source page has ≤ 2 total links (peripheral) but target has ≥ 8 (hub) — connecting a loose page to a load-bearing concept |
| Partial name match | +1 | "graph" appears but page is knowledge-graphs — plausible but ambiguous |
Confidence labels
Tag each candidate with a confidence label based on its score:
| Score | Label | Action |
|---|---|---|
| ≥ 6 | EXTRACTED | Link is effectively certain — exact mention or very strong match. Apply inline. |
| 3–5 | INFERRED | Link is a reasonable inference — shared context, cross-category, peripheral→hub. Apply inline or as Related section. |
| 1–2 | AMBIGUOUS | Weak or partial match. Skip unless user specifically a |