backlinks — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited backlinks (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Audit the vault's backlink structure to surface orphaned notes, dead links, and one-way connections — the value is in finding what the knowledge graph has lost or never built.
Don't: use this to find conceptual bridges — that's /connect. Don't auto-fix findings — surface for Shane to act on.
task: "Vault access (bash only, no MCP tools): obsidian search query='TERM' limit=10, obsidian read file='Note Name' (no .md), obsidian backlinks file='Note Name'. Audit the vault's backlink structure around '[argument]' (or broadly). Find orphaned notes, broken connections, and opportunities to strengthen the knowledge graph."skill: "backlinks"If Qwen is unavailable:
[argument] is provided, run obsidian search query='[argument]' limit=10 via bash; otherwise run broad searches (e.g. obsidian search query='MOC OR index OR hub' limit=20) via bash to sample the vaultobsidian read file='[note name]' via bash for each — look for [[wikilinks]] and [[note references]] embedded in them[[link]] in other notes[[links]] that reference notes that don't exist yet[argument], analyze the local backlink cluster; if broad, sample across the vault~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.