curator

Fixes broken wikilinks and malformed frontmatter in Obsidian vaults within per-run budgets.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/MilUX-Ltd/footing --skill curator-milux-ltd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: curator
Source: https://github.com/MilUX-Ltd/footing/tree/main/footing/template/Skills/meta-skills/curator
Command: npx skills add https://github.com/MilUX-Ltd/footing --skill curator-milux-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Knowledge vaults accumulate small mechanical defects over time: wikilinks broken by renames, missing or malformed frontmatter, and unescaped pipes in table links. Individually none justify a work session, but together they erode trust in the vault. This Skill performs a budgeted hygiene sweep that fixes unambiguous defects and reports everything requiring judgement. ## Core Features & Use Cases - Budgeted Mechanical Fixes: Repairs broken wikilinks with exactly one matching target, fills derivable frontmatter fields, and escapes pipes in table wikilinks, capped at 20 fixes and 200 file reads per run. - Decision Report: Writes a dated Curation Report in Operations listing every fix plus up to 30 ranked items needing human judgement, such as stale statuses, possible duplicates, and orphan pages. - Scheduled or On-Demand Runs: Designed to run monthly as a scheduled task or interactively, rotating folder coverage across runs for large vaults. - Use Case: Run a monthly sweep of your Obsidian business vault so broken links from renamed pages get fixed automatically while questionable items like long-inactive engagements are surfaced for your review. ## Quick Start Ask the assistant to run the curator and sweep the vault for broken links and frontmatter defects.

Frequently Asked Questions about curator

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

FAQPage Schema
How do I fix broken wikilinks in an Obsidian vault automatically?▼

Run the curator sweep, which detects wikilinks whose targets no longer exist and repairs them only when exactly one page in the vault matches, such as after a rename or move. Ambiguous or unmatched links are listed in the Curation Report instead of being guessed.

What does a vault hygiene sweep check for?▼

The sweep checks for broken wikilinks, missing or malformed frontmatter against each folder's Guide conventions, and unescaped pipes in table wikilinks. It also reports stale statuses, possible duplicates, orphan pages, and abandoned last_reviewed dates for human decision.

Can the curator delete or rename files in my vault?▼

No. The curator never deletes anything and never renames files, since renames break links elsewhere. Filename convention violations are only recommended in the report, and deletion is treated as an exclusively human action.

What happens when the vault is too large for one sweep?▼

The curator reads at most 200 files per run and rotates coverage across folders. Each report records which folders were swept and which were skipped, so the next run continues where the previous one stopped.

Why does the curator limit fixes to 20 per run?▼

Hard budgets keep unattended runs reviewable: 20 fixes and 30 report items can be checked in minutes, while an uncapped run making hundreds of changes would be an incident. Hitting a cap stops that activity and is noted in the report.