AB fragments
Fragmented work logging and idea capture powered by Memos. Full memo lifecycle: create, search, update, delete, and comment. Daily-log: structured work journal in .plan format. Passive trigger: after agent completes a task, prompt user to record. Active trigger: user says "memo", "note", "capture", "daily log", "fragments", "记录", "笔记", "日志", "想法", "评论", "comment", "更新 memo", "删除 memo".
As a process B 65/100 · Nearly there — 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: 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 65/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 26 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1032 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low The skill ranks results itself: that belongs to the system behind the tool, not the model
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 388: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 26 items
- +4Reference files are cited in the instructions (7 of 7)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.