AC llm-wiki-health-score
当用户要求审计、评分、评估或监控 Obsidian/个人知识库是否符合卡帕西式 LLM Wiki 架构，或要求 WorkBuddy/Codex 对本地 Vault 生成知识库健康分、结构化信号和语义抽样最终评分时使用。关键词：LLM Wiki、Obsidian、个人知识库、健康分、语义抽样、WorkBuddy。
当用户要求审计、评分、评估或监控 Obsidian/个人知识库是否符合卡帕西式 LLM Wiki 架构，或要求 WorkBuddy/Codex 对本地 Vault 生成知识库健康分、结构化信号和语义抽样最终评分时使用。关键词：LLM Wiki、Obsidian、个人知识库、健康分、语义抽样、WorkBuddy。
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 35 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1050 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low The response is described with custom markup (4 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 156: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.