CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

debug-issue

Systematically debug issues using graph-powered code navigation

Quality

78%

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/debug-issue/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 is an exemplar of lean, actionable, tool-driven guidance with a clear sequence and good organization. The only gap is the absence of explicit validation/feedback checkpoints, which keeps workflow_clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — five terse tool-call steps plus a tight token-budget section — with no over-explanation of concepts Claude already knows, matching the score-5 anchor.

5 / 5

Actionability

Each step is a concrete, executable tool invocation with real arguments (e.g. query_graph_tool with callers_of/callees_of, get_minimal_context_tool(task="..."), detail_level="minimal"), fully matching the copy-paste-ready score-5 anchor.

5 / 5

Workflow Clarity

A clear numbered 1-5 sequence with ordering rules is present, but there are no explicit validation checkpoints or feedback loops; this fits score-4 rather than 5, and the destructive/batch cap does not apply since the workflow is investigative and read-only.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references, and its sections (Debug Issue, Steps, Token Efficiency Rules) are well-organized, satisfying the simple-skill exception for a score of 5.

5 / 5

Total

19

/

20

Passed

Description

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

The description conveys a clear, niche capability (graph-powered debugging) but omits any "when to use it" trigger guidance, which caps completeness and limits trigger-term quality. It is specific and distinctive but not self-activating.

Suggestions

Add an explicit "Use when…" clause listing trigger phrases such as debugging, tracing bugs, or investigating call chains.

Broaden trigger terms with synonyms like "bug", "troubleshoot", and "trace" so users' natural phrasing matches the skill.

Mention concrete actions (trace call chains, find entry points, assess fix impact) to lift specificity toward the multi-action anchor.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ("debug issues", "graph-powered code navigation") but coverage is not comprehensive, matching the score-3 anchor rather than the multi-action score-4 anchor.

3 / 5

Completeness

A clear "what" is present (debugging via graph navigation) but there is no "when"/"Use when…" clause, which the guidelines cap at 3.

3 / 5

Trigger Term Quality

"debug issues" is a natural term a user would say, but common synonyms and variations (bug, troubleshoot, trace, investigate) are missing, fitting the score-3 anchor rather than the broad-coverage score-4.

3 / 5

Distinctiveness Conflict Risk

"graph-powered code navigation" is a fairly niche, distinguishing niche with only minor overlap risk against generic debugging skills; it does not reach a 5 because no explicit trigger phrases are given to fully minimize conflict risk.

4 / 5

Total

13

/

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

tirth8205/code-review-graph

Path

skills/debug-issue/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.