Diagnose and fix GitHub Actions CI failures. Inspects workflow runs and logs, identifies root causes, implements minimal fixes, and pushes to a fix branch. Use when CI is failing, red, broken, or needs diagnosis.
98
Does it follow best practices?
Validation for skill structure
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 well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually say, explicitly addresses both what the skill does and when to use it, and carves out a distinct niche around GitHub Actions CI troubleshooting.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Inspects workflow runs and logs, identifies root causes, implements minimal fixes, and pushes to a fix branch.' These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Diagnose and fix GitHub Actions CI failures. Inspects workflow runs...') AND when ('Use when CI is failing, red, broken, or needs diagnosis') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'CI failures', 'GitHub Actions', 'CI is failing', 'red', 'broken', 'diagnosis'. These cover common variations of how users describe CI problems. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on GitHub Actions CI failures with distinct triggers like 'workflow runs', 'CI failing', 'red'. Unlikely to conflict with general coding or other DevOps 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 an excellent skill file that demonstrates best practices across all dimensions. It provides concrete, executable commands for each step of the CI debugging workflow, maintains appropriate scope without over-explaining, and includes important safety guardrails. The verification step and deliverable format ensure Claude knows when the task is complete.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary commands and guidance without explaining what CI is or how GitHub Actions work. Every section earns its place with actionable content. | 3 / 3 |
Actionability | Fully executable bash commands throughout with specific flags and options. Commands are copy-paste ready with clear placeholders for variable values like <run-id> and <branch>. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence with explicit verification step at the end. Includes feedback loop (verify fix, rerun if needed) and safety notes for risky operations like workflow permissions. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections that progress logically from diagnosis to fix to verification. Content is appropriately sized for a single file without needing external references, and the deliverable section provides clear output expectations. | 3 / 3 |
Total | 12 / 12 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
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
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.