CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

debugging

Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles and locking the fix with a failing test. Use for crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior, or reverse engineering.

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplar of progressive disclosure: a lean index with verified references, a crisply sequenced phase loop with strong validation gates, and concrete navigation. The main weakness is redundancy — the mandate to read the references is repeated to the point of padding, which costs token efficiency without adding information.

Suggestions

Collapse the repeated read-the-references messaging into a single statement of the gate rule: the 🚨 section, "If you cannot honestly say...", and the "Skipping one costs an hour" line all restate it, and "What to Do Right Now" repeats instructions already given in the Runtime Setup and Phase Loop sections.

Trim the rhetorical enforcement padding ("you are doing it wrong", "THIS IS NOT OPTIONAL", "not modify-then-remember-maybe") to plain directives — the tables and invariants carry the same force without the emphasis.

Fold the "What to Do Right Now" section into the intro or cut it to just the first-read ordering (runtime reference → matching tool references → 00-setup.md), since the phase loop table already specifies what to read when.

DimensionReasoningScore

Conciseness

The body is mostly lean tables and pointers assuming Claude's competence, but the read-the-references injunction is restated many times (the 🚨 section, the gate rule, "If you cannot honestly say...", "Skipping one costs an hour", and the "What to Do Right Now" section repeating prior instructions). This goes beyond minor trimming — anchor 3 ("includes some unnecessary explanation or could be tightened") fits better than 4.

3 / 5

Actionability

Concrete navigation throughout: exact per-runtime/per-tool/per-phase file paths, a copy-paste-ready bundled-vs-native discriminator ("du -h ./target" plus a full "strings -n 12 ./target | rg -i '...'" command), and a numbered immediate-action list. Not a 5 because most executable substance lives in the references and the body's own runnable commands are limited to the one discriminator.

4 / 5

Workflow Clarity

The phase loop (0–10) is a clearly sequenced process with explicit validation checkpoints: root cause confirmed only by toggling the cause, fix locked by a failing test, feedback loop after 2 failed rounds (Oracle Triple), journal-tracked cleanup verified by "git diff shows only fix + test", and four final evidence gates. Matches the anchor-5 example with feedback loops and checklists.

5 / 5

Progressive Disclosure

The body is a pure index with well-signaled, one-level-deep references: every runtime, tool, and phase row links to a specific file in references/, and all linked files (including scripts/dap.mjs and the partial-runtime-evidence.md anchor) exist in the bundle. Content is appropriately split with easy per-scenario navigation — a clear anchor-5 match.

5 / 5

Total

17

/

20

Passed

Description

88%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 description in third-person voice that pairs a concrete multi-action what with an explicit Use-for clause of natural trigger phrases. The only gaps are a few missing common trigger synonyms and slight overlap risk on the reverse-engineering trigger.

DimensionReasoningScore

Specificity

"Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles and locking the fix with a failing test" names multiple concrete actions (hypothesis-driven loop, oracle escalation, fix locked by a failing test) covering the debugging workflow end-to-end. Not a 4 because coverage of the what is comprehensive across the loop rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both: what ("Runs a hypothesis-driven debugging loop... locking the fix with a failing test") and when ("Use for crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior, or reverse engineering") with concrete trigger phrases. Matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

"Use for crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior, or reverse engineering" gives good natural-phrase coverage users would actually say. Not a 5 because common variations like "bug", "error", "exception", "stack trace", or "flaky test" are missing; not a 3 because the terms present are exactly the natural phrasing users use for failures.

4 / 5

Distinctiveness Conflict Risk

Debugging with failure-specific triggers (crashes, hangs, memory leaks) is a clear, mostly distinct niche. Not a 5 because "reverse engineering" and "wrong responses" are triggers that could also fire for a dedicated reverse-engineering or API-testing skill, creating minor overlap risk with closely related skills.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 22 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 21 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

code-yeongyu/lazycodex

Path

plugins/omo/skills/debugging/SKILL.md

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.