AA AI Output Failure Triage
Diagnose why an AI response failed, identify missing context, and prepare a safer retry prompt with acceptance checks and a go/no-go recommendation.
As a process A 84/100 · Runs to the end — weak spots: consistency, running it twice, progress reporting
How to improve
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: 3. 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) - note
frontmatter-keyunknown frontmatter key "type"
Process rating: all ten parameters 84/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (AI Output Failure Triage) differs from the folder (ai-output-failure-triage)
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 74 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 5 branches, has a failure section
- 100Execution cost. Instruction body is 1977 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +1No license
- +2Single-language instructions
- +3Description length 148: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 74 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.
External checks
ClawHub: clean
This is a prompt-only triage skill with no code, network, credentials, or persistence; users should still avoid pasting confidential material into failed-output examples.
LLM: benign (high) · VirusTotal: benign · 14 May 2026