CtrlK
BlogDocsLog inGet started
Tessl Logo

fix-gh-actions

Investigate and fix failing GitHub Actions checks for this repo or its PRs. Use when the user asks to debug CI failures, broken workflows, failed release jobs, or failing GitHub checks.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary lean, instruction-only skill: crisp sequencing, real decision rules, explicit validation, and zero token waste. The only notable gap is the absence of concrete commands for inspecting run logs, which is the central activity of the task.

DimensionReasoningScore

Conciseness

Every line carries instruction ("Classify the failure as flake, infra, or real before any action"; "Retry a suspected flake one time. A second identical failure is a defect"). No padding, no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Contains a concrete executable command ("git merge-base --is-ancestor origin/main HEAD"), a specific status URL, and crisp decision rules, but no example commands for the core log-inspection step (e.g. gh run view / gh run watch). Instruction-only guidance is otherwise actionable; matches "mostly executable with minor gaps".

4 / 5

Workflow Clarity

An 8-step numbered sequence with explicit checkpoints: classify before acting, check githubstatus when many jobs fail, rebase instead of retry on a stale base, and "Re-run targeted validation and report residual risk" as a closing validation step. Not a destructive/batch operation, so no validation cap applies.

5 / 5

Progressive Disclosure

A 19-line single-file skill with no need for external references; per the rubric's simple-skill exception, well-organized sections suffice. The content is appropriately self-contained, and the one cross-skill pointer ("also use github-action-review") is clearly signaled.

5 / 5

Total

19

/

20

Passed

Description

78%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 description: clear what/when structure with concrete, natural trigger phrases anchored to a specific domain. The main gap is thin action coverage (only investigate/fix) and missing common trigger synonyms like "build failures" or "pipeline".

Suggestions

Enumerate the concrete activities performed, e.g. "Investigate failing jobs, read workflow logs, classify failures as flake/infra/defect, and fix root causes in workflow files" — this would lift specificity from 3 to 4-5.

Add common user phrasings to the trigger clause such as "build failures", "red CI", or "broken pipeline" to broaden natural keyword coverage.

Consider mentioning inspection of run logs or the GitHub CLI since log analysis is the core of the task and currently unmentioned.

DimensionReasoningScore

Specificity

"Investigate and fix failing GitHub Actions checks for this repo or its PRs" names the domain plus two concrete actions (investigate, fix), but coverage stops there rather than enumerating several specific actions. Not 4: the good-examples pattern lists multiple concrete operations, while this names only the two.

3 / 5

Completeness

Explicitly answers both questions: what ("Investigate and fix failing GitHub Actions checks for this repo or its PRs") and when ("Use when the user asks to debug CI failures, broken workflows, failed release jobs, or failing GitHub checks") with concrete trigger phrases. Clearly matches the top anchor.

5 / 5

Trigger Term Quality

"debug CI failures, broken workflows, failed release jobs, or failing GitHub checks" gives good natural keyword coverage users would actually say. Not 5: misses common variations such as "build failures", "pipeline is red/broken", or "CI is down".

4 / 5

Distinctiveness Conflict Risk

GitHub Actions is a clear niche with distinct triggers, but "debug CI failures" is generic enough to overlap with a general CI-debugging skill. Minor overlap risk matches the 4 anchor rather than the minimal-conflict 5 anchor.

4 / 5

Total

16

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fallow-rs/fallow
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.