CtrlK
BlogDocsLog inGet started
Tessl Logo

systematic-debugging

Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body delivers a well-sequenced, concrete debugging methodology with strong validation checkpoints and clean organization. Its main weakness is minor redundancy between the principle, red-flags, and warning-signs sections plus an unverifiable success-rate claim.

Suggestions

Trim redundancy: merge "Red Flags - Process Violations" and "Warning Signs of Deeper Problems" into a single stop-conditions section, since both restate the "no fix without root cause" principle.

Remove or substantiate the "~95% first-time fix rate vs ~40%" claim in Success Metrics, as it is unsourced and reads as padding.

Consider condensing the four "Common Debugging Scenarios" code blocks into a compact table or a single reference section to reduce token overhead while preserving actionability.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence, but the "Red Flags" and "Warning Signs" sections restate the core principle and the unsourced "~95% first-time fix rate" in "Success Metrics" is padding, so it could be tightened.

2 / 3

Actionability

As an instruction-only skill it provides concrete, specific procedural guidance (numbered steps, "git bisect", "Add validation at the source", "check shared mutable state"), which the rubric rewards without requiring code.

3 / 3

Workflow Clarity

A clear four-phase sequence with explicit validation checkpoints and feedback loops ("If fix fails, STOP", "THREE or more fixes fail consecutively, STOP", verify-then-suite) matches the anchor for well-sequenced workflows.

3 / 3

Progressive Disclosure

With no bundle files present, the content is well-organized into clearly labeled sections with no nested or deep references; the only cross-link (testing-patterns) points to another skill rather than a chained bundle.

3 / 3

Total

11

/

12

Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly conveys both purpose and triggering contexts using natural, user-voiced terms, with an explicit "Use when" clause. It is slightly more generic on specific concrete actions, which keeps specificity at 2 rather than 3.

DimensionReasoningScore

Specificity

"Four-phase debugging methodology with root cause analysis" and "investigating bugs, fixing test failures, troubleshooting unexpected behavior" name the domain and several actions, but they remain generic rather than the multiple specific concrete operations of a score-3 anchor.

2 / 3

Completeness

It states what the skill does ("Four-phase debugging methodology with root cause analysis") and gives an explicit "Use when..." trigger clause, satisfying both what and when.

3 / 3

Trigger Term Quality

Terms like "bugs", "test failures", and "troubleshooting unexpected behavior" are natural phrases users would actually say when they need debugging help, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

Debugging is a clear niche with distinct triggers (bugs, test failures, troubleshooting) that are unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ChrisWiles/claude-code-showcase
Reviewed

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.