cross-linker weaves a wiki’s knowledge graph tighter. It builds a registry of page names, titles, aliases and tags, scans every page for unlinked mentions and shared context, and scores each candidate link.
Strong and reasonable candidates are applied as inline wikilinks or a Related section, each with a relationship type such as uses or extends. It also scores pages in a misc folder against projects and reports promotion candidates, then ends with a report of what changed.
What You Get
- Inline wikilinks added at the first natural mention, or a Related section as fallback
- A relationships block in frontmatter with a type for each added link
- A cross-link report listing links added, remaining orphans and misc promotion candidates
- A git snapshot taken before any write, when the vault is its own repository
Common Use Cases
- Run after a large ingest to connect the new pages
- Reduce orphan pages in a vault
- Find which pages in misc belong to a project
- Prepare a vault for graph export with typed relations
What Makes It Unique
It scores links with named signals and confidence labels, writes a semantic relationship type for each link, and builds its registry from frontmatter, reading full pages only where a mention needs checking. It also takes a git snapshot of the vault before writing and tells the user how to undo the run.
Under The Hood
The skill is instructions for the agent. It reads the vault config, index and log, globs and reads markdown pages, and edits them in place to add wikilinks and frontmatter. When the vault is its own git repository, it runs git add and git commit to snapshot first, and it documents git reset and clean commands to discard the run if the user wants. It calls the obsidian-wiki command line to sync the log and hot cache, and runs qmd to refresh a search index when one is configured. It makes no web requests.