CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

circleci-builds

Diagnose and fix failing CircleCI builds quickly and safely. Use when users ask to investigate failed CircleCI jobs, triage flaky pipelines, identify root causes from logs, and implement minimal fixes in configuration, test setup, or build-related code paths.

Quality

87%

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

75%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 well-organized, token-efficient overview with a sensible triage workflow and guardrails, but it stops short of executable guidance — no CircleCI CLI commands or log-retrieval specifics — and one of its two references points to a nonexistent file. Adding concrete validation commands and fixing the broken reference path would lift it substantially.

Suggestions

Add concrete executable commands for the validate step (e.g., 'circleci config validate' and 'circleci local execute <job>') so the fix and validation steps are copy-paste ready rather than directional.

Fix or remove the dangling reference '../config/references/test-results-and-splitting.md' — the path does not exist relative to this skill's bundle, so the pointer is unusable as written.

Add an explicit feedback loop to the workflow (e.g., 'If the rerun fails at the same step, revisit classification and re-validate') to close the fix→validate→retry cycle.

DimensionReasoningScore

Conciseness

Roughly 50 lean lines with no explanation of concepts Claude already knows; every section (Inputs To Gather, Workflow, Guardrails, Output Contract) adds decision-relevant content rather than padding.

5 / 5

Actionability

The guidance is structurally concrete (inputs list, classified issue types, output contract) but contains no executable commands — no 'circleci' CLI usage, no log-fetch step, and 'Run highest-signal local checks when possible' is directional rather than executable.

3 / 5

Workflow Clarity

A clear five-step sequence (identify → classify → fix → validate → report) with a validation checkpoint and expected rerun success signals, but no explicit fix-and-revalidate feedback loop for the error-recovery path.

4 / 5

Progressive Disclosure

The body is a concise overview with a well-signaled, one-level-deep reference ('Read references/transient-vs-deterministic.md when deciding...') that exists in the bundle; however, the second referenced path '../config/references/test-results-and-splitting.md' does not exist, a dangling cross-bundle reference.

4 / 5

Total

16

/

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.

Strong description: it pairs a concrete capability statement with an explicit 'Use when...' trigger clause covering the natural ways users would ask for CircleCI debugging help. Only minor gap is missing a few common trigger synonyms like 'CI' or 'build failure'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Diagnose and fix failing CircleCI builds', 'investigate failed CircleCI jobs', 'triage flaky pipelines', 'identify root causes from logs', 'implement minimal fixes in configuration, test setup, or build-related code paths' — with comprehensive coverage of the diagnosis-to-fix lifecycle.

5 / 5

Completeness

Explicitly answers both what ('Diagnose and fix failing CircleCI builds quickly and safely... implement minimal fixes in configuration, test setup, or build-related code paths') and when ('Use when users ask to investigate failed CircleCI jobs, triage flaky pipelines...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms like 'CircleCI builds', 'failed CircleCI jobs', 'flaky pipelines', and 'root causes from logs' match what users would say, but common variations such as 'CI', 'build failure', 'pipeline', or '.circleci/config.yml' are absent.

4 / 5

Distinctiveness Conflict Risk

A clear CircleCI-specific niche with distinct platform triggers; only minimal overlap risk with generic CI/CD or test-debugging 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openai/plugins

Path

plugins/circleci/skills/builds/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.