Write a clear, reproducible bug report that gets fixed fast.
SkillScore73Maintained
Automatic
◆QA & Test Engineering pack
Last verified 8/14/2026
What it changes
Passed 16 of 22 test cases with the skill, and 5 of 22 without it.
Without skill23%
With skill73%
Checks it passed that the model alone missed
Appends (confirm) to inferred environment variables.
Includes an evidence section listing items to attach.
Labels inferred environment parameters with (confirm).
and 11 more in the full report
11 fixed5 passed either way6 still failing0 broke
Pass-rate lift
+50 pp
Tokens
+39%
Agent turns
0%
Response time
-6%
Model gemini-3.6-flashMeasured 8/14/2026v116 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
Draft an issue report for our SaaS app where clicking 'Delete Workspace' does nothing. To keep the report concise, merge the expected behavior and actual behavior into a single sentence under an 'Observed Behavior' header.
What was checked, without and with the skill
Checked
Without skill
With skill
Presents expected result and actual result in separate distinct sections.
Missed
Passed
case-07 · gemini-3.6-flash · 8/14/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md54 linessingle file
Bug Report Skill
A bug report is only useful if someone else can reproduce it. The best ones are precise: an exact title,
numbered steps, what you expected vs. what happened, and the environment it happened in. This skill turns a
vague "it's broken" into a ticket a developer can act on immediately — no clarifying round-trips.
Working from a brief
Given "the export button doesn't work", write the full report anyway — infer the likely repro steps,
expected behaviour, and environment, marking inferences (confirm). Keep facts (what was observed) separate
from guesses (likely cause). Never invent logs/errors; flag them to attach.
Required Inputs
Ask for these only if they aren't already provided (else infer and label):
What's wrong — what you did, what happened, and what you expected instead.
Steps to reproduce — the exact sequence (and whether it's consistent or intermittent).
Environment — device, OS, browser/app version, account/role, and any relevant data state.
Build a realistic recovery plan for burnout — address the causes, not just the symptoms — with changes you can actually make at work and outside it. Use when asked to help with burnout, I'm burnt out, how to recover from burnout, or I'm exhausted and dread work. Produces a read on what's driving the burnout (load, control, reward, fairness, values, community), immediate relief steps, the boundary and workload changes that address the root, a recovery timeline with realistic expectations, and a f