CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-fix-ci

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

79

1.00x
Quality

88%

Does it follow best practices?

Impact

33%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-structured skill body with an explicit sequenced workflow, validation checkpoints, and proper offloading of detail to a bundled script. The main weakness is redundancy from restating the description and repeating the script invocation multiple times.

Suggestions

Remove or compress the Overview paragraph since it restates the frontmatter description verbatim, letting the Workflow section carry the operational detail.

Show the bundled script invocation once in Quick start and reference it by name in the Workflow and Bundled Resources sections instead of repeating the full command multiple times.

Consider moving the manual gh-command fallback (workflow step 3) into a short reference block or the script's --help, keeping the main workflow lean.

DimensionReasoningScore

Conciseness

The Overview paragraph restates the frontmatter description verbatim, and the bundled script invocation is repeated roughly five times across Quick start, Workflow, and Bundled Resources — mostly efficient but could be tightened.

3 / 5

Actionability

Fully executable, copy-paste-ready commands throughout (gh auth status, gh pr view --json, gh run view --log, gh api .../logs, and the script with --json/--max-lines/--context flags) covering the common cases.

5 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation (auth check in step 1), an approval gate before implementing (step 6-7), error-recovery fallbacks (field drift, in-progress runs), and a recheck feedback loop (step 8).

5 / 5

Progressive Disclosure

Clear sectioned overview with a well-signaled one-level-deep reference to the real bundled scripts/inspect_pr_checks.py; the heavy logic is appropriately split into the script file rather than inlined.

5 / 5

Total

18

/

20

Passed

Description

92%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 well-crafted description with explicit trigger guidance, concrete actions, and clear scope boundaries that distinguish it from related skills. The only minor gap is coverage of common synonyms like 'CI'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval'), giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what (inspect/summarize/plan/implement) and when via a concrete 'Use when a user asks to debug or fix failing GitHub PR checks' trigger clause.

5 / 5

Trigger Term Quality

Strong natural terms ('debug or fix failing GitHub PR checks', 'GitHub Actions') but missing common synonyms users say such as 'CI', 'build failing', or 'tests failing'.

4 / 5

Distinctiveness Conflict Risk

Clear niche scoped to GitHub Actions PR checks, explicitly excluding external providers (Buildkite), minimizing overlap with adjacent skills.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
foryourhealth111-pixel/Vibe-Skills
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.