CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fix-bug

Resolves one bug from any evidence (Dash0 link, stack trace, error, file:line, screen recording, Linear ticket, or symptom): triages complexity, locks a failing repro, runs root-cause analysis, and at confidence >= 92 % hands off to a verified draft PR via the fast or standard lane. Flags --analyse-only, --force-holistic, --verify-deploy <PR>; triggers on "/fix-bug".

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

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 unusually well-engineered orchestrator body: precise gates, literal commands, and real feedback loops make the workflow unambiguous and highly actionable. Its one material defect is delivery: nearly every rules/ and templates/ file it routes to is absent from the bundle, breaking the progressive-disclosure structure it is built around.

Suggestions

Include the referenced rules/ (16 files) and templates/ (2 files) in the skill bundle, or inline the critical ones — as delivered, every phase's deep-dive link is a dead path and the routing design cannot function.

Add a packaging check that validates every relative link in SKILL.md resolves to a real bundle file before the skill is shipped.

Deduplicate the ledger-lifecycle explanation (Phase 0.5 vs Step 2d) and state the CEGIS 3-round cap once, in the Phase 6 lane table, to tighten the body further.

DimensionReasoningScore

Conciseness

The body is dense and high-signal — regex detection rules, decision tables, numeric thresholds — and assumes competence (no explanation of what git bisect or a stack trace is). Not a 5 because of trimmable redundancy: the ledger-creation lifecycle is spelled out in both Phase 0.5 and Step 2d, and the CEGIS round-cap/fallback is repeated across Phase 6; not a 3 because there is no padded or already-known-concept explanation anywhere.

4 / 5

Actionability

Much of the guidance is literal and executable: exact commands ("git rev-parse --abbrev-ref HEAD", "gh pr view --json url,isDraft,headRefName 2>/dev/null", "git bisect run <repro-command>"), exact regexes for input classification, exact error strings and thresholds. Falls short of 5 because many phases defer their executable procedure to rules/*.md files (e.g., "Run the probes in rules/preflight.md") that are not present in the delivered bundle, leaving those steps as pointers rather than executable guidance.

4 / 5

Workflow Clarity

Ten phases are explicitly sequenced with mechanical validation gates (Step 5a reproduction gate, Step 6.pre protected-branch assertion, Step 7.pre draft-PR assertion) and explicit feedback loops: gate failure returns to Phase 2.5, sub-90% confidence re-traces the weakest hop, lightweight-analysis failure upgrades simple→complex, and fast-lane CEGIS failure falls back to the standard lane. This matches the top anchor: clear sequence, explicit validation, error-recovery loops, and failure-triggered lesson writes.

5 / 5

Progressive Disclosure

The in-body structure is good — it is a genuine overview with clearly signaled, one-level-deep references and a stated purpose for each — but scored against the actual bundle, only 2 of ~20 referenced files exist (references/design-rationale.md, references/research-sources.md); all 16 rules/*.md and 2 templates/*.md targets are missing, so most deep-dive navigation is dangling. Unresolved reference targets are more than the 'minor organization gaps' of the 4 anchor, while the SKILL.md itself properly defers detail rather than inlining it, keeping it above the 2 anchor.

3 / 5

Total

16

/

20

Passed

Description

80%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: concrete, action-dense, third-person, and honest about scope, with distinctive evidence-form triggers. The main gaps are the absence of natural-language invocation triggers beyond the literal slash command and a few missing common synonyms (crash, exception, regression).

DimensionReasoningScore

Specificity

Enumerates concrete pipeline actions — "triages complexity, locks a failing repro, runs root-cause analysis" and "hands off to a verified draft PR via the fast or standard lane" — plus the accepted evidence forms (Dash0 link, stack trace, error, file:line, screen recording, Linear ticket, symptom). This is comprehensive coverage of multiple specific actions, matching the top anchor rather than the 'several actions, minor gaps' anchor below it.

5 / 5

Completeness

The 'what' is explicit and concrete, and "triggers on \"/fix-bug\"" is explicit trigger guidance, so the missing-'Use when' cap at 3 does not apply. Not a 5 because the 'when' is limited to the slash command — there is no natural-language trigger clause (e.g., 'use when the user reports a bug or pastes a stack trace') telling Claude when to invoke it unprompted.

4 / 5

Trigger Term Quality

Good natural-term coverage: "bug", "stack trace", "error", "screen recording", "Linear ticket", "symptom" are phrases users actually say. Falls short of the 5 anchor because common synonyms and variations ("crash", "exception", "regression", "failing test") are missing, but is well above the 3 anchor since multiple natural keywords are present.

4 / 5

Distinctiveness Conflict Risk

The niche is mostly distinct — confidence-gated, repro-first bug resolution with distinctive triggers (Dash0, Linear, telemetry-verified fix). Minor overlap risk remains with generic debugging/tdd/code-review skills it composes with because "any evidence ... or symptom" is broad; not a 5, but clearly more distinct than the 'somewhat specific' 3 anchor.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 35 missing, 1 suspicious

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

skills/workflow/fix-bug/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.