Obsidian Vault Linkerv1.0.4

A researcher or lifelong learner points the agent at their Obsidian vault to surface hidden connections between notes across different domains. The agent reads notes first, reports candidate relationships like contradictions and supersessions, and writes typed wikilinks only after approval.

A software team maintains architecture decision records and incident postmortems in an Obsidian vault. The agent discovers causal chains such as a decision that led to an incident, plus prerequisite relationships between runbooks, making the decision history navigable.

A PhD student uses the agent to map supports, contradicts, and disputes relationships across literature notes before writing a paper. It flags cross-domain connections between methodology notes and domain-specific findings that the student missed.

A consultancy's internal vault of engagement notes and frameworks benefits from the agent spotting sibling topics and parent/child hierarchies across practice areas. Consultants browse typed links to reuse prior work instead of re-deriving frameworks.

A power user runs the agent in autonomous overnight mode to supersede stale notes, fix orphan notes, and add follow/precede links in project logs. A summary report of every added relationship is reviewed the next morning.

The core skill is free and open-source on GitHub, driving adoption among PKM enthusiasts. Revenue comes from paid setup engagements and custom relationship-type tuning for teams with domain-specific vocabularies.

A hosted layer indexes vaults in the cloud, running scheduled relationship discovery and delivering reports via email or dashboard. The local free skill remains available, with the hosted tier charging for continuous autonomous runs and multi-vault support.

Targets small companies that want a shared, queryable graph of internal docs without adopting a heavy platform. Pricing is per-seat with an annual contract, including onboarding and periodic relationship audits of the vault.