CtrlK
BlogDocsLog inGet started
Tessl Logo

circleci-cli

Operate and troubleshoot CircleCI using the CircleCI CLI. Use when users ask to authenticate CLI access, inspect pipeline/workflow/job status, validate configuration locally, rerun pipelines/jobs, trigger pipelines, or gather actionable diagnostics from CLI outputs.

75

Quality

92%

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

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 guarded workflow, but several workflow steps describe actions by intent rather than giving exact executable CLI commands, which limits actionability.

Suggestions

Add concrete, copy-paste-ready command forms for the key workflow steps (e.g., the exact 'circleci pipeline list' / 'circleci pipeline run' invocations with typical flags) instead of describing them by intent.

Show an example of extracting the first failing scope/step from a real command's output format so the diagnostics step is unambiguous.

Make the validation checkpoint an explicit gate rather than conditional ('Validate config locally when relevant') — e.g., always run 'circleci config validate' before mutating changes.

DimensionReasoningScore

Conciseness

The body is lean with no concept padding, assumes Claude's competence, and every line earns its place; it avoids the verbosity that would drop it to 2.

3 / 3

Actionability

A few concrete commands appear ('circleci help', 'circleci pipeline list|create|run', 'circleci trigger ...'), but most workflow steps describe intent ('Inspect available...state', 'Extract first failing scope') rather than copy-paste executable commands, matching the 'some concrete guidance but incomplete' anchor. Not 3 because guidance is not fully executable; not 1 because real specifics are present.

2 / 3

Workflow Clarity

A clearly sequenced five-step process with explicit read-first ordering, an auth/CLI verification checkpoint, a validation step, and a final report-and-next-action feedback loop — matching the clear-sequence-with-validation anchor for mutating operations.

3 / 3

Progressive Disclosure

A short, single-file skill under 50 lines with no need for external references, organized into clearly labeled sections (Overview, Workflow, Guardrails, Output Contract), which per the simple-skills note can score 3.

3 / 3

Total

11

/

12

Passed

Description

100%

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, trigger-rich, and clearly distinguishes both what the skill does and when to use it, hitting the top anchor on every dimension.

DimensionReasoningScore

Specificity

Enumerates many concrete actions — 'authenticate CLI access', 'inspect pipeline/workflow/job status', 'validate configuration locally', 'rerun pipelines/jobs', 'trigger pipelines', 'gather actionable diagnostics' — matching the multiple-specific-actions anchor rather than the partial-domain anchor at 2.

3 / 3

Completeness

Clearly states what it does ('Operate and troubleshoot CircleCI using the CircleCI CLI') and includes an explicit 'Use when...' clause with concrete triggers, satisfying both the what and the when.

3 / 3

Trigger Term Quality

Uses natural phrasing a user would say ('authenticate', 'inspect...status', 'validate configuration', 'rerun pipelines/jobs', 'trigger pipelines') with good coverage and common variations, matching the strong trigger coverage anchor.

3 / 3

Distinctiveness Conflict Risk

Scoped specifically to the CircleCI CLI with distinct trigger verbs, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
openai/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.