debugger
Bug hunter - finds and fixes issues quickly
43
Quality
25%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/debugger/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague to be useful for skill selection. It lacks specific actions, natural trigger terms, explicit usage guidance, and distinctiveness. The casual tone ('Bug hunter') and brevity provide almost no information for Claude to determine when to select this skill over others.
Suggestions
Add specific concrete actions: e.g., 'Analyzes stack traces, debugs runtime errors, identifies memory leaks, traces code execution paths'
Include a 'Use when...' clause with natural trigger terms: e.g., 'Use when the user mentions bugs, errors, exceptions, crashes, debugging, or asks to fix broken code'
Specify the scope/technology to reduce conflicts: e.g., 'for Python/JavaScript applications' or 'in backend services' to distinguish from other debugging skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('finds and fixes issues') without specifying concrete actions, tools, or what types of bugs/issues it handles. No specific capabilities are listed. | 1 / 3 |
Completeness | Partially addresses 'what' (finds and fixes issues) but very weakly. Completely missing 'when' guidance - no 'Use when...' clause or explicit trigger conditions. | 1 / 3 |
Trigger Term Quality | Contains only generic terms like 'bug' and 'issues' without natural variations users might say (e.g., 'debug', 'error', 'crash', 'exception', 'stack trace', 'troubleshoot'). Missing file types or technology context. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'issues' could apply to any debugging, testing, code review, or troubleshooting skill. Would conflict with many other development-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a general debugging framework with some useful code snippets, but suffers from explaining concepts Claude already knows (bug categories, what debugging tools exist) and lacks the concrete, actionable specificity that would make it truly useful. The methodology is sound but abstract, and the content would benefit from being more focused on project-specific debugging patterns rather than general programming knowledge.
Suggestions
Remove or drastically reduce the 'Common Bug Categories' section - Claude already knows these; instead focus on project-specific debugging patterns or tools
Add concrete validation checkpoints to the debugging methodology (e.g., 'Run test suite after fix: `npm test`')
Replace the persona framing with actionable content - the 'You are Debugger' introduction wastes tokens
Make the 'Bug Report Analysis' section actionable with a concrete example showing input bug report and expected analysis output
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary framing ('You are Debugger, the bug-fixing specialist') and categorical lists that Claude already knows (common bug categories, debugging tools). The code examples are useful but the surrounding explanations could be tighter. | 2 / 3 |
Actionability | Provides some concrete code examples (null checks, async handling, logging), but much of the content is descriptive lists rather than executable guidance. The debugging methodology is abstract steps without specific commands or tools to execute. | 2 / 3 |
Workflow Clarity | The 6-step debugging methodology provides a sequence, but lacks validation checkpoints or feedback loops. No explicit verification steps between stages or guidance on what to do if a step fails. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. For a skill of this length (~80 lines), some content (like the full bug categories list) could be referenced externally or trimmed. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- TurnaboutHero/oh-my-antigravity
- Commit
fab464f
- 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.