CtrlK
BlogDocsLog inGet started
Tessl Logo

bug-hunter

Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.

54

Quality

61%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/bug-hunter/SKILL.md

The canonical home for this skill is bug-hunter in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

56%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 skill is actionable and well-sequenced with a clear debugging workflow, but it is padded with basic programming concepts Claude already knows and inlines reference material that should be split into bundled files.

Suggestions

Remove or condense the "Common Bug Patterns" and "Debugging Techniques" sections, which re-explain basic concepts (off-by-one, type coercion, async/await) Claude already knows.

Move the Common Bug Patterns, Debugging Tools, and Documentation Template material into separate reference files (e.g., references/patterns.md, references/tools.md) linked one level deep from SKILL.md.

Add explicit error-recovery feedback loops (e.g., "if reproduction fails, gather more environment info") to the workflow steps to reach the validation standard.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: the "Common Bug Patterns" and "Debugging Techniques" sections explain basic concepts Claude already knows (off-by-one, type coercion, async/await, rubber-duck, print debugging), adding padding beyond what the skill should contribute.

2 / 5

Actionability

Concrete executable code and commands appear throughout (bash log checks, git bisect, javascript logging/debugger snippets, test examples), with only minor gaps such as illustrative pseudocode hypotheses and trace diagrams.

4 / 5

Workflow Clarity

The 8-step debugging process is clearly sequenced with a verify-the-fix step and reproduction feedback loop, but most steps lack explicit error-recovery feedback loops, keeping it just below the 5 anchor.

4 / 5

Progressive Disclosure

The body is well-sectioned with headers, but at ~370 lines with no bundle files it inlines substantial reference material (Common Bug Patterns, Debugging Tools, Documentation Template) that belongs in separate one-level-deep files.

3 / 5

Total

13

/

20

Passed

Description

66%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 states concrete capabilities clearly in third person but omits any explicit "when to use" trigger guidance, which caps its completeness. It is specific and distinct but would benefit from a Use-when clause.

Suggestions

Add an explicit "Use when..." clause naming natural triggers such as bug reports, errors, crashes, or "debug this" requests to raise completeness and trigger-term coverage.

Include a few more natural synonyms (error, crash, exception, failing test) to broaden trigger-term quality.

Remove the redundant "fixes"/"implements fixes" phrasing to tighten specificity.

DimensionReasoningScore

Specificity

"finds and fixes bugs", "Traces from symptoms to root cause, implements fixes, and prevents regression" lists several concrete actions across the debugging domain, though "fixes" and "implements fixes" overlap, leaving minor coverage gaps versus the comprehensive 5 anchor.

4 / 5

Completeness

The description clearly answers "what" (find/fix bugs, trace root cause, prevent regression) but contains no "Use when..." clause or explicit trigger guidance, capping completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

"bugs" and "debugging techniques" are natural terms users say, but common variations like "error", "crash", "debug this", or "not working" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Debugging is a clear niche with distinct triggers and minimal conflict risk, though broad overlap with general code-review or fix skills keeps it just below the maximally distinct 5 anchor.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Path

plugins/AI-Agents-Safe-Coding-Skills/skills/bug-hunter/SKILL.md

Commit

57c135b

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill