AC obsidian-wiki
Build and maintain a compiled LLM Wiki inside an Obsidian vault following Karpathy's pattern. Use when working with an Obsidian vault as a persistent knowledge base: ingesting raw sources into `raw/`, compiling or updating interlinked wiki pages under `wiki/`, generating an index, linting for broken links/orphans/staleness, maintaining taxonomy/schema files, or answering questions from pages already compiled into the wiki. NOT for: general Obsidian note-taking or plugin management (use `obsidian` skill), simple note creation, vault syncing, or generic Q&A that doesn't involve a compiled wiki vault.
As a process C 64/100 · Has gaps — weak spots: result and completion, running it twice
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 64/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 6 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 4 branches
- 100Steps. 55 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2762 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (9 tags): a typed call is more reliable
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
- +3Output format is not stated: the model decides each time
- -31 of 10 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 605: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 55 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.