| name | audit_links |
| description | Validate vault graph consistency and structural integrity |
🔍 Audit Links Skill
Fast audit of vault structure to catch:
- Orphan papers (not linked to any project)
- Orphan projects (not linked to any MOC)
- Broken bidirectional links (paper→project without reciprocal project→paper)
- Forbidden concept links (e.g.,
[[Attention Mechanism]])
- Papers linking directly to MOCs (forbidden)
- Malformed wiki links
CRITICAL RULES
Vault constraints (non-negotiable):
- Every paper in
Reading/ must link to ≥1 project in Projects/
- Every project in
Projects/ must link to ≥1 MOC in MOCs/
- Bidirectional links: If paper→project exists, project→paper must exist
- Papers never link directly to MOCs
- Papers link only to projects and other papers
- Concept/method/technique links forbidden (e.g.,
[[Transformer]], [[Attention Mechanism]])
WORKFLOW
1. Get audit scope
Read .claude/vault_maintanance.md and note the audit_links: timestamp.
Default: incremental scan — only files modified after the audit_links: timestamp.
Use find Reading/ Projects/ MOCs/ -newer <reference_file> to scope the file set.
To use a reference file, write the timestamp as a temp file: touch -t YYYYMMDDHHMI /tmp/audit_ref && find ... -newer /tmp/audit_ref
Only run a full scan if:
- The user explicitly requests it ("full audit", "scan everything")
