AF knowledge-health-checker
Audit and improve Markdown knowledge-base health across Obsidian, Logseq, Notion exports, docs folders, and wiki repositories. Detect empty placeholder notes, broken wiki links, weak content density, orphan notes, graph fragmentation, stale files, and repair opportunities. Generate health scores, actionable reports, and safe fix plans. Use for knowledge base audit, wiki lint, broken link detection, Obsidian vault cleanup, markdown graph health, content quality review, and documentation garden maintenance.
As a process F 51/100 · Will not run — References files that are not bundled: path.md, ../path/file.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Concealment
en-hide-from-userSKILL.md:223Instruction to hide actions from the user (negated — the text forbids it)Never silently delete or rewrite knowledge files.
negated
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: path.md - warning
missing-refreference to a missing file: ../path/file.md - note
frontmatter-keyunknown frontmatter key "last_updated" - note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 51/100
- 0Tools and files. 2 referenced file(s) missing: path.md, ../path/file.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 100Steps. 75 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2118 tokens
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 510: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 75 items
- +3Output format is stated explicitly
- +4Has examples (10 code blocks)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.