AC bug-hunter
Bug analysis, reproduction, and reporting assistant. Analyze logs, stack traces, screenshots to identify root cause. Generate structured bug reports with severity, priority, reproduction steps, and expected vs actual behavior. Use when: (1) analyzing error logs or stack traces, (2) writing bug reports, (3) triaging bugs, (4) reproducing issues, (5) root cause analysis, (6) "分析这个bug", "写bug报告", "看看这个报错", "帮我定位问题", "崩溃分析". NOT for: fixing code (use coding tools), writing test cases (use test-case-gen), or project management.
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 2. 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 59/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
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1519 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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 528: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.