CtrlK
BlogDocsLog inGet started
Tessl Logo

debugging

Systematic debugging methodology with root cause analysis. Phases: investigate, hypothesize, validate, verify. Capabilities: backward call stack tracing, multi-layer validation, verification protocols, symptom analysis, regression prevention. Actions: debug, investigate, trace, analyze, validate, verify bugs. Keywords: debugging, root cause, bug fix, stack trace, error investigation, test failure, exception handling, breakpoint, logging, reproduce, isolate, regression, call stack, symptom vs cause, hypothesis testing, validation, verification protocol. Use when: encountering bugs, analyzing test failures, tracing unexpected behavior, investigating performance issues, preventing regressions, validating fixes before completion claims.

72

Quality

90%

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-5

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

A well-structured overview skill that sequences a four-phase debugging workflow with explicit verification checkpoints and clean one-level-deep progressive disclosure. Minor conciseness redundancy and high-level (rather than in-body executable) guidance are the only weaknesses.

Suggestions

Trim the restated Core Principle sentence ('Random fixes waste time...') since the bold NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST line already conveys it, and consider whether the Quick Reference adds enough over the Four Techniques section to earn its tokens.

Add one short inline executable example (e.g., a sample find-polluter.sh invocation or a reproduce→isolate command pattern) so the body is actionable without requiring a reference load for common cases.

Narrow the 'When to Use' scope (e.g., drop or qualify 'investigating performance issues') to reduce overlap with dedicated performance/testing skills.

DimensionReasoningScore

Conciseness

Mostly lean overview, but the Core Principle is restated as 'Random fixes waste time and create new bugs...' and the Quick Reference re-routes the same Four Techniques, giving minor redundancy that could be trimmed.

4 / 5

Actionability

Concrete phased guidance (Phase 1–4 with sub-steps), a real referenced script (scripts/find-polluter.sh), and explicit 'Load when' triggers give mostly executable direction, though deep executable detail is delegated to references.

4 / 5

Workflow Clarity

A clearly sequenced four-phase process with a gate ('Complete each phase before proceeding'), an explicit validation checkpoint ('Iron law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE'), and a feedback loop (Red Flags → return to process).

5 / 5

Progressive Disclosure

A clear overview points to four one-level-deep reference files plus one script, each signaled with references/X.md and a 'Load when:' trigger; all referenced files exist and a Quick Reference provides navigation.

5 / 5

Total

18

/

20

Passed

Description

96%Weight 40%Scale 1-5

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

A strong, explicit description that clearly states what the skill does and when to use it, with comprehensive concrete actions and natural trigger terms. Its only weakness is slight scope breadth that risks minor overlap with adjacent perf/testing skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'backward call stack tracing, multi-layer validation, verification protocols, symptom analysis, regression prevention' plus explicit 'Actions: debug, investigate, trace, analyze, validate, verify bugs' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both 'what' (methodology, phases, capabilities, actions) and 'when' ('Use when: encountering bugs, analyzing test failures, tracing unexpected behavior...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural keywords a user would actually say — 'debugging, root cause, bug fix, stack trace, test failure, reproduce, isolate, regression, breakpoint' — with synonyms, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Debugging is a clear niche with distinct triggers, but scope broadens into 'investigating performance issues' and 'analyzing test failures,' creating minor overlap with dedicated perf/testing skills rather than minimal conflict risk.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
samhvw8/dot-claude
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.