CtrlK
BlogDocsLog inGet started
Tessl Logo

fix-ci

Find failing PR checks, inspect logs or external check links, and apply focused fixes

62

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured with a clear iterative workflow and feedback loop, but actionability is held at 2 because log inspection and fix application lack a concrete worked example beyond the single gh command.

Suggestions

Add a short worked example showing how to extract the first actionable error from a GitHub Actions log line.

Give one concrete example of a "smallest safe fix" (e.g. a one-line config or dependency bump) to lift actionability toward copy-paste ready.

Optionally note the exact gh subcommand for viewing a job's log (e.g. gh run view --log-failed) so the inspect step is fully executable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it does not explain CI, gh, or logs — and every section (Trigger, Workflow, Guardrails, Output) earns its place.

3 / 3

Actionability

One concrete executable command is given ("gh pr checks --json name,bucket,state,workflow,link"), but log inspection and "apply the smallest safe fix" remain instruction-level with no worked example, leaving key details unspecified.

2 / 3

Workflow Clarity

A clear 4-step numbered sequence is paired with an explicit validation checkpoint and feedback loop ("Push, re-check the PR check set, and repeat until green"), satisfying sequence, validation, and retry for a simple skill.

3 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, references no external files, and is organized into clear sections, so progressive disclosure scores 3 without needing bundle references.

3 / 3

Total

11

/

12

Passed

Description

60%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and third-person with concrete actions, but lacks an explicit "Use when..." trigger clause and broader natural keyword coverage, capping completeness and trigger quality at 2.

Suggestions

Add an explicit "Use when..." trigger clause, e.g. "Use when a branch or PR has failing CI checks."

Broaden trigger terms to include common phrasings like "CI", "failing tests", "build failures", or "red checks".

Tighten distinctiveness by naming the scope boundary (e.g. GitHub PR checks specifically) to reduce overlap with general debugging skills.

DimensionReasoningScore

Specificity

The description lists three concrete actions — "Find failing PR checks", "inspect logs or external check links", and "apply focused fixes" — matching the multiple-specific-actions anchor rather than a single domain mention.

3 / 3

Completeness

The "what" is clearly stated, but there is no "Use when..." or equivalent explicit trigger, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Terms like "failing PR checks", "logs", and "check links" are natural, but common variations users would say ("CI", "failing tests", "build failures", "red checks") are missing.

2 / 3

Distinctiveness Conflict Risk

The PR-CI-failure niche is fairly specific, but without an explicit trigger clause and given possible overlap with general debugging or git-fix skills, conflict risk is not fully eliminated.

2 / 3

Total

9

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
cursor/plugins
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.