AD action-bias
Stop agents from producing reports instead of taking action. Restructure prompts, cron jobs, and agent shifts so they DO things — send emails, post content, make API calls, push code — instead of writing plans about doing things. Use when: agents keep outputting strategy docs instead of executing, sub-agent sessions produce reports nobody reads, you notice your crew is busy but nothing external is happening, heartbeat/shift results are all 'here's what we should do' with no proof of doing it, or you want to audit whether your agents are actually shipping.
As a process D 48/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: 4. 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 48/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
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1468 tokens
- 100Running it twice. Mutating operations check current state
- 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 561: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.