CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fix-ci

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

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./cursor-team-kit/skills/fix-ci/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean, well-structured instruction skill with a concrete core command, clear sequencing, and an explicit push-recheck feedback loop. The only notable gap is the unspecified command for fetching failed-job logs.

DimensionReasoningScore

Conciseness

Every line earns its place: a trigger, four workflow steps, guardrails, and an output spec with zero padding or explanation of concepts Claude already knows. Lean and efficient, matching the anchor-5 example.

5 / 5

Actionability

Step 1 gives a concrete executable command ("gh pr checks --json name,bucket,state,workflow,link") and the workflow is instruction-only, so lack of code is not penalized. However, "inspect failed jobs and extract the first actionable error" omits the concrete log-fetching command (e.g., "gh run view --log-failed"), leaving minor gaps.

4 / 5

Workflow Clarity

The four steps are clearly sequenced with an explicit feedback loop ("Push, re-check the PR check set, and repeat until green") and a one-failure-at-a-time guardrail. Validation between fix and push is implicit rather than an explicit checkpoint, matching anchor 4.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references (none exist in the bundle), and is organized into clear sections (Trigger, Workflow, Guardrails, Output) — the simple-skill exception for a score of 5 applies.

5 / 5

Total

18

/

20

Passed

Description

58%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 moderately strong description with concrete, domain-specific actions and clear distinctiveness. Its main weakness is the missing explicit "when to use" trigger clause and limited natural-language synonyms ("CI", "build failure") for reliable activation.

Suggestions

Add an explicit trigger clause, e.g., "Use when PR or branch CI checks are failing, a build is red, or the user asks to fix CI."

Include natural synonyms such as "CI", "build failure", and "failing checks" so the description matches how users actually phrase the request.

Consider mentioning the iterate-until-green behavior ("push and repeat until checks pass") to round out capability coverage.

DimensionReasoningScore

Specificity

"Find failing PR checks", "inspect logs or external check links", and "apply focused fixes" are three concrete actions in a specific domain. Minor coverage gaps (e.g., iterating/pushing until green) keep it below the comprehensive anchor 5.

4 / 5

Completeness

The description has a clear "what" but no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"PR checks" and "logs" are relevant natural terms, but common variations users would say — "CI", "build failure", "red checks", "broken pipeline" — are missing. Keyword coverage is partial rather than good, matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

The PR-check/CI niche with tool-specific terms ("PR checks", "check links") is mostly distinct with only minor overlap risk against general debugging or code-fix skills.

4 / 5

Total

14

/

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

cursor/plugins

Path

cursor-team-kit/skills/fix-ci/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.