audit_links

Detect orphan papers, broken bidirectional links, and forbidden paper-to-MOC links in vault graphs.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/D0miH/claudsidian --skill audit-links
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit_links
Source: https://github.com/D0miH/claudsidian/tree/main/.claude/skills/audit_links
Command: npx skills add https://github.com/D0miH/claudsidian --skill audit-links

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vault graphs often drift with orphan papers and projects, broken links, and forbidden connections, making discovery unreliable and maintenance costly.

Core Features & Use Cases

  • Orphan detection: identify papers in Reading/ with no linked Projects/
  • Orphan projects: identify Projects/ not linked to any MOC
  • Bidirectional link validation: ensure paper→project has reciprocal project→paper
  • Forbidden link detection: flag direct paper→MOC links and concept-like links
  • Remediation guidance: surface actionable fixes and a concise report

Quick Start

Run audit_links to scan Reading/, Projects/, MOCs/, and maintenance metadata and generate a remediation report

Frequently Asked Questions about audit_links

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find orphan papers in my Obsidian vault?

You can find orphan papers by auditing vault graph consistency to detect files in Reading/ that have no linked entries in Projects/. The audit scans your maintenance metadata and surfaces these disconnected nodes in a remediation report.

What is the best way to validate bidirectional links between papers and projects?

Validating bidirectional links requires auditing your vault graph to ensure every paper→project link has a reciprocal project→paper link. The audit checks Reading/ and Projects/ directories to flag broken connections and provide actionable fixes.

How do I detect forbidden direct links from papers to MOCs?

Detecting forbidden direct paper→MOC links involves auditing your vault graph consistency to enforce relationship rules. The scan flags any direct connections between Reading/ and MOCs/ directories, along with concept-like links, for immediate remediation.

Why do I have orphan projects not linked to any MOC?

Orphan projects occur when vault graphs drift over time, leaving Projects/ files without links to MOCs/. Auditing your vault graph consistency identifies these disconnected projects and generates actionable steps to link them properly.

Can I audit vault graph consistency without setting up maintenance metadata?

Auditing vault graph consistency relies on scanning maintenance metadata alongside Reading/, Projects/, and MOCs/ directories. Without this metadata, the audit cannot fully verify relationships or surface accurate remediation steps for your vault graph.

What vault graph integrity rules should I enforce for research notes?

Key vault graph integrity rules include ensuring every paper links to at least one project, every project links to at least one MOC, and reciprocal paper→project links exist. Auditing enforces these non-negotiable rules and flags forbidden concept links.