Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ledgerhq/console-log
Convention for console logging levels across the monorepo.
Passed 22 of 24 test cases with the skill, and 16 of 24 without it.
and 3 more in the full report
6 fixed16 passed either way2 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.
In our single-page web app, background analytics beacon requests occasionally drop when a user closes the tab mid-request. The error cannot be retried nor fixed. How should we handle logging this error in the catch block? Write the catch block code.
| Checked | Without skill | With skill |
|---|---|---|
| The catch block contains no console logging statements. | Missed | Passed |
The instructions your model reads when the skill loads.
console.error is intercepted by monitoring tools (Datadog RUM, Sentry) and forwarded as an error event.
console.warn for expected or recoverable errors (network failures, optional feature unavailable, etc.)console.error only for illegal/unexpected program states that should never occur in productiontest cases passed, vs 16 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.