CtrlK
BlogDocsLog inGet started
Tessl Logo

etiology

Bug-fix discipline — every defect has an etiology, the chain of cause that produced the observable fault; trace it before patching. Errors only grow: a bandaid leaks unless genuinely localized and leak-free. Walk the diagnostic ladder (presentation → proximate cause → API contract → isolated or systemic) before writing the fix. Use when authoring or reviewing any bug fix, regression patch, "quick fix" PR, or when deciding whether to ship, defer, or refactor.

68

Quality

81%

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

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.

A tight, well-structured instruction skill that gives a concrete diagnostic procedure and crisp decision criteria rather than abstract advice. It assumes Claude's competence and avoids padding; the main gap is the absence of a worked example showing the ladder applied end-to-end.

Suggestions

Add one short worked example (a real bug traced through presentation → proximate cause → API contract → isolated/systemic) to lift actionability and workflow_clarity.

Add an explicit post-fix verification step (e.g., 're-run the regression test; confirm no adjacent call site regresses') to complete the workflow feedback loop.

Trim the opening paragraph's overlap with the description to push conciseness toward 5.

DimensionReasoningScore

Conciseness

Lean and opinionated with no explaining of basics Claude already knows, but the opening 'Errors only grow' paragraph partially restates the description and the 'short version' repeats the body, giving minor trimmable redundancy.

4 / 5

Actionability

Provides concrete actionable guidance — the four numbered ladder rungs each pose a specific question, and the bandaid test gives two precise conditions (Localized, Leak-free) — but lacks a worked example tracing a real bug through the ladder.

4 / 5

Workflow Clarity

The diagnostic ladder is a clearly sequenced four-step process with an explicit checkpoint ('Stating in the PR description which rung you stopped at — and why') and a deferral revisit-loop, but there is no post-fix verification feedback loop.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (diagnostic ladder, coverage, bandaid conditions, deferral, short version) with the 'short version' acting as an overview; no external references are needed for this conceptual skill, though a worked-example file could deepen it.

4 / 5

Total

16

/

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: it states the discipline, lays out a concrete four-rung diagnostic procedure, and gives explicit 'Use when' triggers with developer-natural phrasing. The only soft spot is minor overlap with generic review/triage skills and a few missing trigger synonyms.

Suggestions

Add a couple more natural trigger synonyms (e.g., 'hotfix', 'incident', 'bug report') to broaden trigger_term_quality.

Sharpen distinctiveness by framing the trigger around the decision ('deciding whether a fix addresses cause vs. symptom') rather than generic 'reviewing any bug fix', which overlaps code-review skills.

DimensionReasoningScore

Specificity

Names concrete actions — 'trace it before patching', 'Walk the diagnostic ladder (presentation → proximate cause → API contract → isolated or systemic)', 'before writing the fix' — giving multiple specific steps with comprehensive coverage of the diagnostic process.

5 / 5

Completeness

Explicitly answers both what ('Bug-fix discipline ... trace it before patching ... Walk the diagnostic ladder') and when ('Use when authoring or reviewing any bug fix, regression patch, "quick fix" PR, or when deciding whether to ship, defer, or refactor') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural developer terms ('bug fix', 'regression patch', 'quick fix PR', 'ship, defer, or refactor') with synonyms, but misses common variations like 'hotfix', 'bug report', or 'incident'.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche around fix-discipline and ship/defer/refactor decisions, but the 'reviewing any bug fix' trigger carries minor overlap risk with general code-review or triage skills.

4 / 5

Total

18

/

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
gridaco/grida
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.