Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →archive228/systematic-debugging
Use for ANY bug, test failure, crash, or unexpected behavior. Forces reproduce-then-isolate before proposing a fix. Stops the agent from guessing.
Passed 8 of 20 test cases with the skill, and 3 of 20 without it.
and 7 more in the full report
6 fixed3 passed either way13 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.
Users are reporting that the shopping cart resets to empty whenever they refresh the checkout page on Safari, throwing `DOMException: QuotaExceededError`. Help me trace this bug down to its actual origin rather than applying a superficial band-aid. End your response with a one-sentence root cause explanation, the minimal fix required, and the test verifying the fix.
| Checked | Without skill | With skill |
|---|---|---|
| Quotes the exact line that throws the exception | Missed | Passed |
| Provides the smallest input or steps to reproduce the error | Missed | Passed |
| Names a single hypothesis before delivering the solution | Passed | Passed |
The instructions your model reads when the skill loads.
The single most expensive agent failure: seeing an error and immediately generating a "fix" based on the error type, without reading what actually happened. Don't.
Read the whole error. The entire message and stack trace. A TypeError can mean a hundred different things — the trace tells you which one. Quote the exact line that throws.
Reproduce it first. If you can't reproduce it, you can't verify a fix. Write the smallest input that triggers it. "I think this fixes it" is gambling, not debugging.
Form one hypothesis, name it. "I think the value is null because the upstream call returns 204 with no body." State it before you touch anything.
Change one thing. Test. Repeat. If you change three things and it works, you don't know which one fixed it — and the other two may have added new bugs.
Fix the root cause, not the symptom. A null check that hides a null is not a fix. Find why it's null. The underlying bug will resurface differently if you only patch the crash.
End with: the root cause (one sentence), the minimal fix, and the test that now proves it.
test cases passed, vs 3 / 20 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.