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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%

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 clean, concise orchestrator with an excellent stop-on-failure feedback loop, but its progressive-disclosure design is undercut because every referenced detail file is missing from the bundle, leaving the actionable bugfix content incomplete from the body alone.

Suggestions

Ship the referenced files (`commands/{command}.md`, `skills/unattended.md`, `skills/controller.md`, `guidelines.md`) in the bundle, or inline the missing content — broken references prevent the progressive-disclosure structure from working.

Add at least one concrete diagnostic/repair step directly in SKILL.md (e.g., how to parse an error log or reproduce a failure) so the skill is actionable before any referenced file is loaded.

Confirm the referenced paths resolve relative to the skill root; the placeholders (`commands/{command}.md`) should map to real per-phase files that exist alongside SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive with no concept explanation Claude lacks; every line instructs ("read…", "execute…", "stop and report"), matching the lean/efficient anchor rather than the somewhat-padded 2.	3 / 3
Actionability	Navigation is concrete (specific file paths and phase commands), but the substantive bugfix guidance — the actual point of the skill — is delegated to referenced files absent from the body, leaving the body's actionable content incomplete; this fits the 2 anchor (concrete but missing key details) rather than fully-executable 3.	2 / 3
Workflow Clarity	A clearly sequenced three-step Quick Start with branching plus an explicit stop-on-failure checkpoint ("stop and report the error… Do not advance… Offer to retry… or escalate") matches the clear-sequence-with-feedback-loop anchor.	3 / 3
Progressive Disclosure	The overview is well-structured with one-level-deep, clearly signaled references, but the referenced files (`commands/{command}.md`, `skills/unattended.md`, `skills/controller.md`, `guidelines.md`) are not present in the bundle, so navigation leads nowhere; per the bundle-structure guideline this caps the score at 2 rather than 3.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 concise, concrete, and complete: it names four specific actions, gives natural-language trigger terms, and explicitly separates what-it-does from when-to-use-it. It is a strong, low-conflict description with no padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "analyzes error logs, traces root causes, implements fixes, and verifies with regression tests" — matching the multi-action anchor rather than the partial domain-only anchor at 2.	3 / 3
Completeness	Explicitly answers both what ("Diagnostic and repair workflow that analyzes error logs…verifies with regression tests") and when ("Use when fixing bugs…") with an explicit trigger clause, matching the 3 anchor rather than the implied-only-when 2.	3 / 3
Trigger Term Quality	Natural user phrasing is well covered — "fixing bugs, debugging runtime errors or exceptions, investigating test failures or crashes, or submitting bug-fix pull requests" — hitting the broad-natural-terms anchor rather than the narrow 2.	3 / 3
Distinctiveness Conflict Risk	Clear bug-fix niche with distinctive triggers (debugging, test failures, bug-fix PRs) unlikely to fire for unrelated skills, matching the distinct-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: flightctl/ai-workflows
Path: bugfix/SKILL.md
Commit: 75ae801

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.