Install any skill in seconds. Free to start, no credit card required.
Get Started Free →archive228/read-the-trace
Extract the actual cause from a stack trace instead of pattern-matching the error type.
Passed 19 of 22 test cases with the skill, and 17 of 22 without it.
2 fixed17 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to configure the `@sentry/node` SDK in Express to ignore 404 errors and sample transactions at 20% rate. What configuration options should be set in `Sentry.init`?
| Checked | Without skill | With skill |
|---|---|---|
| Specify `ignoreErrors` and `tracesSampleRate` in `Sentry.init` configuration options. | Missed | Passed |
The instructions your model reads when the skill loads.
LLMs love to see "TypeError" and generate a generic fix without reading the trace. Don't.
test cases passed, vs 17 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.