cross-linker
Find and add missing cross-references between wiki pages
Install / Use
npx skills add Ar9av/obsidian-wiki --skill cross-linkerInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of cross-linker
cross-linker scores 88/100 on our quality scale, 1513th of 2,790 Automation skills we index.
Its SKILL.md is 15 KB long, well organised into 23 sections with 14 code examples: a thorough specification that gives an agent plenty to work with.
With 3,485 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so cross-linker is actively maintained.
- Our last check on 2026-11-01 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β read the skill file before letting an agent act on it.
cross-linker compared with similar skills
All 4 of these similar skills score higher than cross-linker; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| cross-linker (this skill)by Ar9av | 88 | 3.5k | 54d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install cross-linker?
- Run
npx skills add Ar9av/obsidian-wiki --skill cross-linker. The install tabs above show the steps for each supported agent. - Which AI agents does cross-linker work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is cross-linker safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is cross-linker still maintained?
- The repository was last updated about 2 months ago, so cross-linker is actively maintained.
Skill content
View source on GitHubname: cross-linker description: > Find and add missing cross-references between wiki pages. Use when pages are disconnected or after large ingestion. This modifies pages to add links; use wiki-lint for report-oriented structural auditing.
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 asks to connect loose pages. |
Only act on EXTRACTED and INFERRED candidates. Include the confidence label in the Cross-Link Report so the user can review INFERRED links before trusting them.
Step 4: Apply Links
Pre-write snapshot β before the first file write, check whether the vault itself is the root of a Git repository. Merely being a subdirectory of a larger repository does not qualify: running git add -A there could capture unrelated files. If the vault is not a standalone Git repository, skip this step silently β no nagging, no suggesting git init.
VAULT_REAL_PATH=$(cd "$OBSIDIAN_VAULT_PATH" && pwd -P)
VAULT_GIT_ROOT=$(git -C "$OBSIDIAN_VAULT_PATH" rev-parse --show-toplevel 2>/dev/null || true)
SNAPSHOT_SHA=""
if [ -n "$VAULT_GIT_ROOT" ] && [ "$VAULT_GIT_ROOT" = "$VAULT_REAL_PATH" ]; then
if git -C "$OBSIDIAN_VAULT_PATH" diff --quiet \
&& git -C "$OBSIDIAN_VAULT_PATH" diff --cached --quiet \
&& [ -z "$(git -C "$OBSIDIAN_VAULT_PATH" ls-files --others --exclude-standard)" ]; then
SNAPSHOT_SHA=$(git -C "$OBSIDIAN_VAULT_PATH" rev-parse HEAD)
else
if ! git -C "$OBSIDIAN_VAULT_PATH" add -A; then
echo "Pre-write snapshot failed; abort the skill without writing any vault files." >&2
exit 1
fi
if ! git -C "$OBSIDIAN_VAULT_PATH" commit -m "pre-cross-linker snapshot" --quiet; then
echo "Pre-write snapshot failed; abort the skill without writing any vault files." >&2
exit 1
fi
SNAPSHOT_SHA=$(git -C "$OBSIDIAN_VAULT_PATH" rev-parse HEAD)
fi
fi
The clean-repository branch deliberately avoids calling git commit, so "nothing to commit" is not treated as an error. If git add or git commit fails, stop before editing the vault; never continue without the promised snapshot.
If SNAPSHOT_SHA is non-empty and the skill writes files, include the SHA in the final report. To discard the entire run, after confirming there are no later changes worth keeping, the user can run:
git -C "$OBSIDIAN_VAULT_PATH" reset --hard "$SNAPSHOT_SHA"
git -C "$OBSIDIAN_VAULT_PATH" clean -fd
For each page with missing links:
4a: Inline linking (preferred)
Find the first natural mention of the term in the body text and wrap it in wikilinks:
Before:
This project uses knowledge graphs to connect entities.
After:
This project uses [[concepts/knowledge-graphs|knowledge graphs]] to connect entities.
Use the [[path|display text]] format when the wikilink path differs from the display text.
4b: Related section (fallback)
If the term isn't mentioned naturally in the body but the pages are semantically related (shared tags, same project), add a ## Related section at the bottom of the page:
## Related
- [[projects/my-project/my-project]] β Also uses AI agents for research automation
- [[concepts/knowledge-graphs]] β Core technique used in this project
If a ## Related section already exists, append to it. Don't duplicate existing entries.
4c: Infer and write relationship type
For every EXTRACTED or INFERRED link added (inline or related section), infer a semantic relationship type from the surrounding sentence context and write it to the page's relationships: frontmatter block. Skip AMBIGUOUS links.
Type inference rules β scan the sentence containing the mention (or, for related-section links, the page title and shared-tag context):
| Sentence pattern | Inferred type |
|---|---|
| "X extends / builds on / generalises Y" | extends |
| "X implements / is an implementation of Y" | implements |
| "X contradicts / opposes / refutes / is at odds with Y" | contradicts |
| "X is derived from / based on / adapted from Y" | derived_from |
| "X uses / relies on / depends on / requires Y" | uses |
| "X replaces / supersedes / deprecates Y" | replaces |
| Shared tags or cross-category inference with no directional cue | related_to |
If the surrounding context is ambiguous or the link came from shared-tag matching (no in-body mention), default to related_to.
Writing the block:
Read the page's YAML frontmatter. If a relationships: block already exists, append new entries without duplicating existing targets. If the block is absent, add it after aliases: (or after tags: when aliases: is missing).
relationships:
- target: "[[concepts/knowledge-graphs]]"
type: uses
Always use wikilink format ([[path/to/page]]) for target values in the relationships: YAML block β regardless of OBSIDIAN_LINK_FORMAT. The OBSIDIAN_LINK_FORMAT setting controls body content; frontmatter properties always use wikilink syntax so that wiki-export can reliably parse them.
Only add entries for links added in this cross-linker run β do not touch typed entries that were already present.
Step 5: Score Misc Page Affinity
After the main linking pass, update affinity scores for all pages in misc/ (pages with promotion_status: misc in their frontmatter, or located under the misc/ directory).
For each misc page:
- Collect outgoing links β all
[[wikilinks]]in the page body - Collect incoming links β grep the vault for
[[misc/<slug>]]and[[<slug>]]references - For each linked page (both directions), check if it belongs to a project:
- Lives under
projects/<project-name>/ - Has a
project:frontmatter field matching a project name
- Lives under
- Group by project name and sum:
outgoing_links + incoming_links - Update the
affinityfrontmatter block on the misc page:
affinity:
obsidian-wiki: 3
another-project: 1
- If any project's score β₯ 3: flag this page as a promotion candidate and record it for the report
Efficiency note: only read the full body of misc pages β other pages only need a frontmatter grep to determine their project membership.
Step 6: Report
Present a summary:
## Cross-Link Report
### Links Added: 23 across 12 pages
| Page | Links Added | Confidence | Placement | Relationship Types |
|---|---|---|---|---|
| `projects/my-project/my-project.md` | 3 | EXTRACTED | 2 inline, 1 related | uses Γ2, related_to Γ1 |
| `entities/jane-doe.md` | 5 | INFERRED | 3 inline, 2 related | extends Γ1, uses Γ3, related_to Γ1 |
| ... | | | | |
### Orphan Pages Remaining: 2
- `references/foo.md` β no incoming or outgoing links found
- `concepts/bar.md` β could not find related p
Truncated for display β read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu β one CLI, zero API fees.
ruflo
81.9kπ The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio β 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6kπ·οΈ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit β see the Safety scan above for what the skill file itself contains.
