CtrlK
BlogDocsLog inGet started
Tessl Logo

oma-debug

Bug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests. Use for bug, debug, error, crash, traceback, exception, and regression work.

69

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, mostly lean agent-skill body with concrete commands and a clear validated workflow, weakened by redundant reference listings and abstract framework jargon that could be trimmed.

Suggestions

Deduplicate the References section: keep a single clearly-labeled list of resources/ and ../_shared/core/ files instead of restating them as prose then bullets.

Drop or briefly justify the 'SSL primitive' and 'Scenes' vocabulary in the Actions table, which reads as framework ceremony rather than actionable guidance.

Make the canonical workflow path more concrete by showing how the rg/Serena commands chain into the reproduction and verification steps rather than leaving 'run the smallest reproduction command first' generic.

DimensionReasoningScore

Conciseness

The body is mostly bullet/table lean, but repeats the references list twice (prose lines 135-139 then a bullet list 140-151) and layers abstract ceremony ('SSL primitive', 'Scenes') that adds jargon overhead Claude does not need.

3 / 5

Actionability

Concrete executable commands are present (`rg "<error-message-or-symbol>"`, `rg --files`, Serena `find_symbol`/`find_referencing_symbols`/`search_for_pattern` calls), with only minor gaps such as the generic 'run the smallest reproduction command first'.

4 / 5

Workflow Clarity

A clear sequenced flow (Entry -> PREPARE/ACQUIRE/REASON/ACT/VERIFY/FINALIZE -> Transitions -> Failure and recovery -> Exit) with an explicit VERIFY checkpoint and a fix-fails-verification feedback loop, though steps stay abstract rather than concrete commands.

4 / 5

Progressive Disclosure

Good section structure with a clearly signaled, one-level-deep references list at the end; no bundle files exist so scoring is on references, and the main gap is the duplicated reference listing rather than nesting.

4 / 5

Total

15

/

20

Passed

Description

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

A strong, third-person description that concretely states multiple capabilities and pairs them with a comprehensive, natural-language 'Use for' trigger clause.

DimensionReasoningScore

Specificity

Lists four concrete actions ('analyzes errors, identifies root causes, provides fixes, and writes regression tests'), giving comprehensive coverage of what the skill does rather than vague language.

5 / 5

Completeness

Explicitly answers both what (analyze/diagnose/fix/test) and when ('Use for bug, debug, error, crash, traceback, exception, and regression work') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms ('bug, debug, error, crash, traceback, exception, and regression') covering the synonyms a user would actually say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (bug diagnosis and fixing) with distinct regression-focused triggers and minimal overlap with feature-building or review skills.

5 / 5

Total

20

/

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
first-fluke/oh-my-agent
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.