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.
100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is a strong skill description that excels across all dimensions. It provides specific concrete actions, comprehensive natural trigger terms users would actually say, explicit 'Use when' guidance, and a distinctive focus on the diagnostic-to-fix workflow. The inclusion of slash commands adds additional clarity for activation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'analyzes error logs', 'traces root causes', 'implements fixes', and 'verifies with regression tests'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('analyzes error logs, traces root causes, implements fixes, verifies with regression tests') and when ('Use when fixing bugs, debugging runtime errors...') with explicit trigger guidance and command list. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'fixing bugs', 'debugging', 'runtime errors', 'exceptions', 'test failures', 'crashes', 'bug-fix pull requests'. Also includes explicit command triggers like /diagnose, /fix, /test. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on diagnostic/repair workflows with distinct triggers. The combination of error analysis, debugging, and bug-fix PR workflow creates a unique profile unlikely to conflict with general coding or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently orchestrates a complex multi-phase bugfix workflow. It provides concrete examples, clear phase transitions with exit criteria, and appropriate progressive disclosure to detailed phase skills. The feedback loops for error recovery and the structured artifact output format demonstrate strong workflow design.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence. No unnecessary explanations of basic concepts; every section serves a clear purpose with minimal padding. | 3 / 3 |
Actionability | Provides concrete, executable bash commands, specific file paths, and a complete markdown template for root-cause documentation. The example session shows exact command sequences that are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear phase sequence with explicit exit criteria for each phase. Includes feedback loops (test fail → return to /fix, review inadequate → return to /diagnose or /fix) and validation checkpoints throughout. | 3 / 3 |
Progressive Disclosure | Excellent structure with quick start overview, then references to one-level-deep files (commands/{command}.md, skills/{name}.md, guidelines.md). Content is appropriately split between overview and detailed phase skills. | 3 / 3 |
Total | 12 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
b213ece
Table of Contents
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.