CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

error-diagnostics-smart-debug

Diagnose software failures using observability data, ranked hypotheses, and targeted instrumentation. Use when the cause is unclear or an issue requires systematic investigation.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/error-diagnostics-smart-debug/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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.

The body presents a well-sequenced 10-step debugging workflow with explicit validation criteria, but is dragged down by circular filler sections, a persona statement, and a pseudocode example built on imaginary functions. Guidance names specific tools and techniques yet rarely gives executable commands, leaving it more descriptive than instructive.

Suggestions

Delete the circular 'Use this skill when'/'Do not use this skill when' sections and the generic 'Instructions' bullets that merely restate the skill name.

Replace the pseudocode example (aiAnalyze, getSentryIssue, getDataDogTraces) with executable commands or real queries, or convert it into concrete non-code instructions.

Drop the persona line ('You are an expert AI-assisted debugging specialist...') and the trailing 'Issue to debug: [user request]' template remnant to tighten token efficiency.

DimensionReasoningScore

Conciseness

The workflow core is dense telegraphic lists, but several padded sections remain: "Working on error diagnostics smart debug tasks or workflows" (circular restatement of the skill name), "Apply relevant best practices and validate outcomes" (generic filler), the persona line "You are an expert AI-assisted debugging specialist", and the trailing "Issue to debug: [user request]" template remnant. Not 2 because there is little over-explanation of concepts Claude already knows; not 4 because the filler sections are clearly trimmable.

3 / 5

Actionability

Specific tools ("Sentry, Rollbar, Bugsnag", "rr/Redux DevTools", "Pyroscope") and techniques ("Canary deploy debug version to 10% traffic") provide real guidance, but the example is pseudocode with non-existent functions (aiAnalyze, getSentryIssue, getDataDogTraces) and many steps describe rather than instruct ("AI suggests optimal breakpoint/logpoint locations"). Not 4 because no executable code or commands are given; not 2 because the tool and technique specifics are concretely actionable.

3 / 5

Workflow Clarity

A 10-step numbered workflow with an explicit validation step and success criteria ("Tests pass", "No performance regression", "Error rate unchanged or decreased") plus falsification criteria for hypotheses. Not 5 because there is no explicit error-recovery loop (e.g., what to do when validation fails or a hypothesis is falsified mid-fix); not 3 because validation checkpoints are explicitly present, not merely implied.

4 / 5

Progressive Disclosure

A single self-contained file with clear section headers (Triage → Observability → Hypotheses → ... → Prevention) and no buried or nested references. Not 5 because at ~194 lines the tool catalogs, production-safety techniques, and worked example could be split into reference files to keep SKILL.md lean; not 3 because the structure is good and content is mostly appropriately placed for a cohesive workflow.

4 / 5

Total

14

/

20

Passed

Description

67%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 solid description that explicitly covers both what the skill does and when to use it, with concrete method-level capability statements. Its main weakness is trigger-term coverage: it lacks the natural vocabulary (debug, error, root cause, stack trace) users would most likely say when they need it.

Suggestions

Add natural trigger terms users would actually say — "debug", "error", "bug", "root cause", "stack trace", "production incident" — to the 'Use when' clause to improve trigger matching.

Make the 'when' clause more concrete with user-facing trigger phrases (e.g., "Use when the user reports an error, crash, or timeout whose cause is unclear") to reach the top completeness anchor.

DimensionReasoningScore

Specificity

"Diagnose software failures using observability data, ranked hypotheses, and targeted instrumentation" names the domain plus three concrete method-level capabilities (observability analysis, hypothesis ranking, instrumentation). Not 5 because these are approach categories rather than a comprehensive list of distinct actions; not 3 because it goes beyond 1-2 actions by naming three specific capability areas.

4 / 5

Completeness

Explicitly answers both: what ("Diagnose software failures using observability data, ranked hypotheses, and targeted instrumentation") and when ("Use when the cause is unclear or an issue requires systematic investigation"). Not 5 because the when-clause states abstract conditions rather than concrete trigger phrases a user would say; not 3 because both what and when are clearly present.

4 / 5

Trigger Term Quality

Relevant phrases like "software failures", "cause is unclear", and "systematic investigation" exist, but the most natural user terms ("debug", "error", "bug", "root cause", "stack trace") are absent. Not 4 because common variations and synonyms users actually say are missing; not 2 because it does include usable condition-based triggers.

3 / 5

Distinctiveness Conflict Risk

The scope condition "when the cause is unclear or an issue requires systematic investigation" distinguishes it from routine bug-fixing and general coding skills. Not 5 because debugging broadly overlaps with general coding-assistance skills; not 3 because the scoping conditions meaningfully narrow the trigger surface.

4 / 5

Total

15

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/error-diagnostics-smart-debug/SKILL.md

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.