CtrlK
BlogDocsLog inGet started
Tessl Logo

debug-like-expert

Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.

70

Quality

85%

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%

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

A well-structured, actionable analysis skill with a clear sequenced workflow, explicit checkpoints, and clean one-level-deep reference navigation. The only notable weakness is repetition of the read-only rule and some motivational filler that could be tightened.

Suggestions

Consolidate the read-only/analysis-only rule into one authoritative statement; remove the repeated 'DO NOT make code changes' reminders in solution_proposal, success_criteria, and decision_gate to recover tokens.

Trim motivational phrasing ('You are a diagnostician, not a surgeon', 'guilty until proven innocent') in favor of concrete guidance, keeping the body lean.

DimensionReasoningScore

Conciseness

Mostly terse and free of basic-concept explanation, but the read-only rule is restated across analysis_only_rule, solution_proposal, success_criteria, and decision_gate, and motivational lines ('diagnostician, not a surgeon', 'guilty until proven innocent') could be trimmed.

2 / 3

Actionability

For an instruction-only skill it gives concrete, copy-paste-ready guidance: exact investigation checklists, a falsifiable hypothesis template, a full output_format markdown template, and a literal decision-gate menu.

3 / 3

Workflow Clarity

A clearly sequenced evidence → root-cause → solution flow with explicit validation checkpoints ('Don't move forward until...'), a yes/no success_criteria gate, and a mandatory decision gate with feedback looping back to further investigation.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview with five well-signaled, one-level-deep references (all verified to exist in references/), each annotated with a content preview in <advanced_topics>; deeper material is appropriately split out.

3 / 3

Total

11

/

12

Passed

Description

85%

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, third-person description with explicit what/when triggers and a distinct escalation niche. Its main gap is the absence of the most natural user term — 'debug'/'debugging'/'bug' — which limits trigger-term coverage.

Suggestions

Add the natural user term 'debug' or 'debugging' to the description (e.g., 'Use when debugging a complex issue and standard troubleshooting fails') so it matches what users actually say.

Consider adding 'bug' or 'hard-to-reproduce bug' as a trigger variation alongside 'root cause analysis' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — 'evidence gathering, hypothesis testing, and rigorous verification' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly states what it does ('methodical investigation protocol...') and includes an explicit 'Use when standard troubleshooting fails or when issues require systematic root cause analysis' trigger, answering both what and when.

3 / 3

Trigger Term Quality

Contains natural terms like 'complex issues', 'standard troubleshooting', and 'root cause analysis', but omits the most common user phrasing ('debug', 'debugging', 'bug'), leaving common variations missing.

2 / 3

Distinctiveness Conflict Risk

The 'when standard troubleshooting fails' qualifier carves a clear escalation niche distinct from general debugging skills, making wrong-skill triggering unlikely.

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
gsd-build/gsd-2
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.