CtrlK
BlogDocsLog inGet started
Tessl Logo

debugging-wizard

Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis.

99

1.07x
Quality

100%

Does it follow best practices?

Impact

98%

1.07x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Evaluation results

99%

10%

Investigate Intermittent Batch Processing Failure

Structured debug output and root cause discipline

Criteria
Without context
With context

Root Cause section

100%

100%

Evidence section

75%

100%

Fix section

100%

100%

Prevention section

70%

100%

No premature fix

100%

100%

Traces data flow

100%

100%

Regression test written

100%

100%

Test is a failing test first

75%

87%

No debug code in corrected script

100%

100%

Single focused fix

70%

100%

100%

16%

Debug a Broken Cart Summary Component

Pattern analysis and hypothesis-driven debugging

Criteria
Without context
With context

Comparison table

66%

100%

Written hypothesis

33%

100%

Root cause identified

90%

100%

Data flow traced

87%

100%

Reproduction pattern noted

100%

100%

Single minimal fix

75%

100%

Fix uses null guard or optional chaining

100%

100%

Test covers undefined cart

100%

100%

Test covers loading state

100%

100%

Root cause before fix

100%

100%

No debug code in fixed file

100%

100%

100%

Investigate a Persistent Regression in the Authentication Service

Three-fix threshold and git bisect regression strategy

Criteria
Without context
With context

Bisect plan present

100%

100%

Correct good commit

100%

100%

Automated bisect

100%

100%

Suspicious commits identified

100%

100%

Three failed patches acknowledged

100%

100%

Architectural problem identified

100%

100%

Structural fix proposed

100%

100%

No symptom patch proposed

100%

100%

Pattern of failures documented

100%

100%

Delta debug cited

100%

100%

No debug code in outputs

100%

100%

100%

9%

Email Notification Worker — Incomplete Delivery Reports

Async bug pattern recognition and fix

Criteria
Without context
With context

Root Cause section

100%

100%

Evidence section

30%

100%

Fix section

100%

100%

Prevention section

75%

100%

Root cause before fix

100%

100%

Correct async iteration fix

100%

100%

Reference to working v1

100%

100%

Regression test covers empty results

100%

100%

Regression test uses async correctly

100%

100%

No debug code in fixed file

100%

100%

Single focused fix

100%

100%

92%

3%

Sales Commission Calculator — Wrong Totals

Time travel debugging and diagnostic instrumentation

Criteria
Without context
With context

Root Cause section

100%

100%

Evidence section

100%

100%

Fix section

100%

100%

Prevention section

100%

100%

Backward tracing described

30%

60%

Root cause before fix

100%

100%

Correct fix applied

100%

100%

Correct output values

50%

50%

Regression test covers tiered calculation

100%

100%

No debug code in fixed file

100%

100%

Single focused fix

100%

100%

100%

2%

Order Processing Pipeline — Intermittent Total Mismatch

Minimal reproduction and binary search isolation

Criteria
Without context
With context

Correct stage identified

100%

100%

Isolation approach described

80%

100%

Evidence of intermediate values

100%

100%

Root cause before fix

100%

100%

Minimal repro is self-contained

100%

100%

Minimal repro demonstrates bug

100%

100%

Correct fix applied

100%

100%

Single focused fix

100%

100%

Regression test covers multi-quantity

100%

100%

No debug code in fixed file

100%

100%

Documented reproduction steps

100%

100%

Repository
jeffallan/claude-skills
Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.