CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gha-diagnosis

Use when GitHub Actions checks fail, workflow runs are red, or user asks to fix CI. Triggers on "fix CI", "actions failing", "checks are red", "pipeline broke", "workflow failed". User may provide a run URL, job ID, or just ask to fix. Commits fixes locally and stops; pass --push to let it push and re-check CI.

76

Quality

95%

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

96%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 excellent operational skill body: phased workflow, executable commands, explicit validation and retry limits, and safety boundaries around pushing that anticipate real failure modes (rejected pushes, unpushed user commits, flaky reappearing failures). The only structural question is whether the triage and pitfalls tables warrant a reference file as the skill grows.

DimensionReasoningScore

Conciseness

Lean and dense — triage and pitfalls are compact tables, commands are bare, and the prose only carries non-obvious operational judgment (detached-HEAD scoping, @{u}..HEAD semantics, rejected-push policy) that Claude does not reliably know. Every token earns its place.

5 / 5

Actionability

Fully executable throughout: 'gh run view <run-id> --log-failed', 'gh run list --branch "$(git branch --show-current)" --status failure --limit 5', 'git log --oneline @{u}..<start commit>', 'gh run watch <databaseId> --exit-status' — copy-paste-ready commands with concrete fallbacks for each input form.

5 / 5

Workflow Clarity

Clear three-phase sequence with explicit validation (verify locally with the same command from the workflow YAML before committing), feedback loops (revert and retry max 3 attempts; re-diagnose after pushed runs fail, max 2 more rounds), and a Rules checklist. The batch operation is fully covered by validation, so no cap applies.

5 / 5

Progressive Disclosure

Well-organized single-file structure with clear sections and no unnecessary external references, and nothing inlined that clearly belongs in a separate file — but at ~90 lines it exceeds the under-50-line simple-skill exception, and the triage/pitfalls tables are borderline reference material. Sits between anchors 4 and 5.

4 / 5

Total

19

/

20

Passed

Description

95%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: it states a distinct niche, explicit trigger conditions with natural user phrasing, and concrete behavior including the default-stops-local safety boundary. The only weakness is that the core fetch/diagnose actions are implicit rather than enumerated.

DimensionReasoningScore

Specificity

Names the GitHub Actions CI domain and several concrete actions ('Commits fixes locally and stops; pass --push to let it push and re-check CI'), but the log-fetch and diagnosis steps are only implied by 'run URL, job ID' — minor gaps in coverage, matching anchor 4 rather than the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both 'what' (commits fixes locally, stops by default, pushes and re-checks CI with --push) and 'when' (Use when checks fail / runs are red / user asks to fix CI) with concrete trigger phrases, matching the anchor 5 example structure.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases — 'fix CI', 'actions failing', 'checks are red', 'pipeline broke', 'workflow failed' — covering synonyms users would actually say, reinforced by the 'Use when GitHub Actions checks fail, workflow runs are red' clause.

5 / 5

Distinctiveness Conflict Risk

Clear niche — GitHub Actions failure diagnosis and fixing — with distinct, domain-specific triggers ('actions failing', 'workflow failed'); minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Validation — 15 / 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

provectus/awos-recruitment

Path

registry/skills/gha-diagnosis/SKILL.md

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.