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"

53

Quality

59%

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 ./.claude/skills/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 body is an efficient, actionable debugging playbook with concrete GitNexus tool calls, a clear sequenced workflow, and a staleness feedback loop. It assumes Claude's intelligence and avoids padding; the main improvement would be consolidating the checklist with the workflow to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with concrete tool calls and no padding about what debugging or indexes are; the only redundancy is the checklist restating the workflow steps, a minor trim opportunity.

4 / 5

Actionability

Concrete, realistic tool calls with arguments (query, context, cypher, trace) plus a worked example give mostly executable guidance, with only minor gaps such as illustrative placeholder strings.

4 / 5

Workflow Clarity

A numbered 0-4 workflow pairs with a checklist and an explicit staleness feedback loop ('If Index is stale -> run analyze'), giving a clear sequence with most checkpoints present; validation is present though slightly implicit for the read-only trace steps.

4 / 5

Progressive Disclosure

Content is well organized into clearly headed sections (When to Use, Bind repo, Workflow, Checklist, Patterns, Tools, Example) with no nested references; as a single-file skill over 50 lines it is well structured but not the idealized one-level-deep reference layout.

4 / 5

Total

16

/

20

Passed

Description

43%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 strong, natural trigger phrasing but omits any statement of what the skill actually does, leaving it as a 'when' without a 'what'. Adding a concrete capability clause (e.g., binding a repo and tracing call chains via GitNexus) would lift completeness and specificity.

Suggestions

Add a 'what' clause before the trigger examples, e.g. 'Traces root causes by binding an indexed repository and following call chains across functions and processes.'

Mention GitNexus or its core tools (query, context, trace, cypher) so the description is distinguishable from generic debugging skills.

Include a few more natural synonyms (e.g., 'stack trace', 'crash', 'exception') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the debugging domain and trigger scenarios ('debugging a bug, tracing an error, or asking why something fails') but states no concrete capabilities or actions the skill performs, landing at the 'names domain but actions minimal or generic' anchor.

2 / 5

Completeness

Only the 'when' is present ('Use when the user is debugging...') with example triggers; there is no statement of what the skill does, matching the 'only when present without what' anchor rather than the level-3 'clear what' anchor.

2 / 5

Trigger Term Quality

Natural trigger phrases like 'Why is X failing?', 'Where does this error come from?', and 'Trace this bug' map well to what a user would actually say, with good keyword coverage though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

'Debugging a bug / tracing an error' is a recognizable niche but the description never names GitNexus or its tooling, so it could still overlap with other code-analysis or debugging skills.

3 / 5

Total

11

/

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
abhigyanpatwari/GitNexus
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.