AD kb_maintenance
Maintain the Research KB team-level overview pages from the Gitea-backed knowledge base. Use for OpenClaw console cron/scheduled maintenance runs that should inspect the existing team KB, reason over recent or important wiki changes, incrementally update only the six overview pages, write hidden maintenance status files for frontend display, and avoid rewriting ordinary knowledge pages.
Maintain the Research KB team-level overview pages from the Gitea-backed knowledge base.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 49/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (kb_maintenance) differs from the folder (kb-maintenance)
- 100Tools and files. No external tools needed
- 100Steps. 38 steps
- 100Execution cost. Instruction body is 1290 tokens
- 100Running it twice. No mutating operations
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -36 of 7 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 389: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.