CtrlK
BlogDocsLog inGet started
Tessl Logo

bugfix

Diagnostic and repair workflow that analyzes error logs, traces root causes, implements fixes, and verifies with regression tests. Use when fixing bugs, debugging runtime errors or exceptions, investigating test failures or crashes, or submitting bug-fix pull requests. Activated by commands: /unattended, /assess, /diagnose, /reproduce, /fix, /test, /review, /document, /pr, /feedback, /start.

69

Quality

85%

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

The canonical home for this skill is bugfix in flightctl/ai-workflows

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a tight, well-structured dispatcher with a clear sequence and error-handling checkpoint, but it relies entirely on referenced bundle files (guidelines.md, commands/*.md, skills/*.md) that are not present, which weakens actionability and progressive disclosure.

Suggestions

Ship the referenced bundle files (guidelines.md, skills/controller.md, skills/unattended.md, and the commands/*.md phase files) so the dispatcher's routing targets actually resolve.

Inline a one-line summary of each phase next to its command reference so the body is actionable even before a referenced file is opened.

Add a brief fallback note for what to do if a referenced file is missing, since the workflow currently cannot proceed without them.

DimensionReasoningScore

Conciseness

The body is lean and efficient (~26 lines), assumes Claude's competence, and contains no concept explanation or padding — every token earns its place as routing logic.

5 / 5

Actionability

It gives concrete file paths and conditional routing ("read `commands/{command}.md` and follow it"), but no bundle files exist so the referenced steps cannot actually be executed, leaving the guidance incomplete like the pseudocode anchor rather than copy-paste ready.

3 / 5

Workflow Clarity

A clear numbered sequence with explicit conditionals and an error checkpoint ("If a step fails... stop and report... Do not advance to the next phase") provides most validation checkpoints, though detailed per-phase validation is delegated to absent referenced files.

4 / 5

Progressive Disclosure

Structure is clear with one-level-deep, well-signaled references (guidelines.md, commands/*.md, skills/*.md), but scoring against the actual bundle reveals no referenced files exist, so navigation points to nothing and could be better backed.

3 / 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.

The description is exemplary: it concisely covers concrete actions, natural trigger terms, both what-and-when, and a distinct niche, all in third-person voice with no fluff.

DimensionReasoningScore

Specificity

"analyzes error logs, traces root causes, implements fixes, and verifies with regression tests" lists multiple specific concrete actions covering the full diagnostic-to-verification lifecycle, matching the comprehensive-coverage anchor.

5 / 5

Completeness

It explicitly states both what ("Diagnostic and repair workflow that analyzes error logs, traces root causes, implements fixes, and verifies with regression tests") and when ("Use when fixing bugs...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"fixing bugs, debugging runtime errors or exceptions, investigating test failures or crashes, submitting bug-fix pull requests" provides comprehensive natural terms with synonyms (bugs/errors/exceptions/crashes) users would actually say.

5 / 5

Distinctiveness Conflict Risk

"bugfix" is a clear niche with distinct triggers (bug-fix PRs, test failures, runtime exceptions) and a command activation list that further differentiates it, giving minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
amir-yogev-gh/ai-workflows
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.