CtrlK
BlogDocsLog inGet started
Tessl Logo

gitnexus-debugging

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/gitnexus/gitnexus-debugging/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is a well-structured, actionable debugging playbook with concrete tool calls, a patterns table, and a worked example. It is concise and assumes Claude's competence, with only minor redundancy and implicit feedback-loop guidance.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanation of concepts Claude already knows; the only minor redundancy is that the Workflow, Checklist, and Tools sections re-cover the same query/context/cypher steps.

4 / 5

Actionability

Concrete, executable tool calls with realistic arguments and a complete worked end-to-end example; held back from 5 because tool-call argument shapes are shown by example rather than formal signatures and the index-refresh command is a bare hint.

4 / 5

Workflow Clarity

A clear 4-step sequence is reinforced by a checklist and a worked example that ends in an explicit root-cause confirmation; the read-only nature means no destructive validation is needed, but the inconclusive-trace feedback loop is only implicit.

4 / 5

Progressive Disclosure

Well-organized single-file skill (~85 lines) with clear section headers and no nested references; at this length the Debugging Patterns table and detailed tool examples could optionally split into reference files, which is the only organization gap.

4 / 5

Total

16

/

20

Passed

Description

51%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 has excellent natural trigger phrases and a clear 'when' clause, but it omits any statement of what the skill actually does, leaving the capability unspecified. This caps completeness and specificity.

Suggestions

Add a concrete capability statement before the 'Use when' clause, e.g. 'Traces bugs through a code graph using query, context, and cypher tools to find execution flows and root causes.'

Mention the key tools (query, context, cypher) or the GitNexus code-graph concept so the description conveys what the skill does, not just when to invoke it.

Tighten distinctiveness by leading with the code-graph/tracing mechanism rather than the generic word 'debugging' to reduce overlap with general debugging skills.

DimensionReasoningScore

Specificity

The description names the domain ('debugging a bug, tracing an error') but names no concrete actions the skill performs — it never mentions the GitNexus query/context/cypher tooling that the body relies on.

2 / 5

Completeness

Only the 'when' is present via the explicit 'Use when...' clause; the 'what' (what the skill actually does) is absent, matching the 'only when without what' anchor.

2 / 5

Trigger Term Quality

Natural user phrases are provided verbatim ('Why is X failing?', 'Where does this error come from?', 'Trace this bug') with good synonym coverage across debugging, tracing, and failure-investigation language.

5 / 5

Distinctiveness Conflict Risk

'Debugging' is a broad activity that overlaps with general code-debugging skills, though the tracing/error-specific trigger examples carve out a recognizable niche.

3 / 5

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mindfold-ai/Trellis
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.