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.

73

Quality

91%

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

82%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 clean, efficient router-style SKILL.md body that sequences a multi-step workflow with an explicit validation checkpoint and points to detailed materials. The main weakness is that all concrete guidance depends on referenced files not present in the reviewed bundle.

Suggestions

Confirm that every referenced path (commands/{command}.md, skills/unattended.md, skills/controller.md, guidelines.md) ships in the skill bundle so the router's guidance is fully actionable.

Add a one-line note clarifying what each referenced file contains (e.g., 'guidelines.md: safety limits and escalation rules') so navigation is unambiguous without opening the files.

Consider stating the expected outcome of each phase (e.g., '/assess: triage and scope the bug') so the sequence remains clear even if a referenced file is missing.

DimensionReasoningScore

Conciseness

Lean ~15-line routing overview with no padding; assumes Claude's competence and every token earns its place.

5 / 5

Actionability

Gives concrete, executable routing — specific file paths ('commands/{command}.md', 'skills/unattended.md', 'skills/controller.md') and named phases — but depends on referenced files that are not present in the reviewed bundle, leaving minor gaps.

4 / 5

Workflow Clarity

Clear numbered decision-tree sequence with an explicit stop-on-failure validation checkpoint and retry/escalate feedback loop; minor gaps because detailed steps live in referenced files.

4 / 5

Progressive Disclosure

Well-structured overview with clearly signaled one-level-deep references, but the referenced paths (commands/, skills/, guidelines.md) are not present in the reviewed bundle so their existence and depth cannot be confirmed.

4 / 5

Total

17

/

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 capabilities and provides explicit, natural trigger phrases for when to use it. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'analyzes error logs, traces root causes, implements fixes, and verifies with regression tests' — with comprehensive coverage of the diagnostic-to-verification lifecycle.

5 / 5

Completeness

Explicitly answers both what ('Diagnostic and repair workflow that analyzes error logs...') and when ('Use when fixing bugs...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural phrases users would say — 'fixing bugs, debugging runtime errors or exceptions, investigating test failures or crashes, submitting bug-fix pull requests' — including synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear bugfix-workflow niche with distinct triggers and command activation list, minimizing overlap with general coding skills.

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