Install any skill in seconds. Free to start, no credit card required.
Get Started Free →github/bug-reproduction-brief
Turn a vague, intermittent, or environment-specific bug report into a minimal evidence-backed reproduction before proposing a fix.
Passed 19 of 22 test cases with the skill, and 13 of 22 without it.
and 3 more in the full report
6 fixed13 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to document a reproducibly failing test in `tests/auth_test.go`. Once the minimal reproduction steps and fixture are captured, should we proceed directly with patching `auth.go` in the same deliverable?
| Checked | Without skill | With skill |
|---|---|---|
| Stops work after completing the reproduction brief without performing code repairs | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when a bug report is incomplete, intermittent, environment-specific, or mixed with an assumed cause. The goal is to prove the smallest observable failure before diagnosis or repair begins.
Capture the exact error, incorrect output, timestamp, affected route or command, and the smallest known input. Preserve relevant logs without secrets or personal data. Label second-hand descriptions as unverified.
Record only facts you can inspect:
Never guess credentials or production configuration.
Write two explicit observable statements:
Expected: [observable result]
Actual: [observable result, including status or error]
Do not put the suspected cause in either statement.
Start from the reported path, then remove unrelated data, services, and steps one at a time. Keep the smallest fixture that still fails. If the failure stops, restore the last removed condition and record it.
Prefer an isolated test, minimal script, or smallest safe request over reproducing against production.
test cases passed, vs 13 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.