BC process-keeper
Backfill project timelines, capture key decisions and fixes, and extract reusable process notes from development work.
Backfill project timelines, capture key decisions and fixes, and extract reusable process notes from development work.
As a process C 61/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
ProcedureSoftware developmentAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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: 9. 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 61/100
- 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
- 30Running it twice. 3 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 64 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 718 tokens
- 100Progress reporting. Reports progress
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)
- +3Description length 118: 120–800 characters recommended
- +4No input/output examples
- +2Single-language instructions
- +4Structure: 12 headings
- +3Step-by-step instructions: 64 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.
External checks
ClawHub: clean
This skill is a coherent process-log helper that reads project context and writes compact notes under docs/process, with no hidden scripts or network behavior found.
LLM: benign (high) · VirusTotal: · 9 Aug 2026