CtrlK
BlogDocsLog inGet started
Tessl Logo

circleci

CircleCI integration. Manage Projects, Users, Organizations. Use when the user wants to interact with CircleCI data.

58

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/circleci/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is highly actionable with executable commands and a solid connection workflow, organized into clear sections. Its main weaknesses are a small amount of introductory background Claude already knows and a dangling 'Step 2' reference that breaks the sequence labeling.

Suggestions

Remove or condense the opening paragraph explaining what CircleCI and CI/CD are, since Claude already knows this.

Fix the dangling 'Step 2' references by labeling the corresponding section ('Step 2: Search for and run actions') or rephrasing to 'skip to Searching for actions'.

Consider moving the large popular-actions table into a referenced file (e.g. ACTIONS.md) to keep SKILL.md a lean overview, which would also improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands and tables, but the opening paragraph explaining what CircleCI/CI-CD is and who uses it is unnecessary background Claude already knows and could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready bash commands for install, login, connection, action search/run, and proxy requests, plus a table of concrete popular actions with keys and descriptions covering the common cases.

5 / 5

Workflow Clarity

The connection flow is clearly sequenced with polling states (READY/BUILDING/CLIENT_ACTION_REQUIRED) and recovery guidance, but it references 'Step 2' which is not actually labeled in the document, and there is no explicit validate-after-run checkpoint for actions.

4 / 5

Progressive Disclosure

Good section structure (Overview, Working with CircleCI, Popular actions, Best practices) with well-organized tables and no nested references, though all content is inlined in one file with no external reference files for the lengthy action table.

4 / 5

Total

17

/

20

Passed

Description

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

The description is clear and distinctively scoped to CircleCI, but it is light on concrete actions and natural trigger terms. Adding explicit verbs (list/trigger/cancel pipelines and workflows) and richer user-facing keywords would raise both specificity and trigger quality.

Suggestions

Replace generic 'Manage Projects, Users, Organizations' with concrete actions, e.g. 'List and trigger pipelines, inspect workflows and jobs, manage contexts and environment variables.'

Expand trigger terms to natural phrases users say: 'CircleCI pipelines, workflows, builds, jobs, contexts, rerun or cancel a workflow.'

Tighten the 'Use when' clause to specific intents, e.g. 'Use when the user wants to inspect or trigger CircleCI pipelines, workflows, or jobs.'

DimensionReasoningScore

Specificity

Names the domain (CircleCI) and a few concrete objects (Projects, Users, Organizations) but these are data entities rather than concrete actions, leaving coverage incomplete with no verbs describing what is done with them.

3 / 5

Completeness

Has a clear 'what' ('Manage Projects, Users, Organizations') and a 'when' clause ('Use when the user wants to interact with CircleCI data'), but the 'what' is thin and the 'when' trigger is somewhat generic, falling short of the explicit concrete-trigger anchor at 5.

3 / 5

Trigger Term Quality

Includes 'CircleCI' and 'interact with CircleCI data' which are relevant, but misses common natural phrases users would say (e.g. 'pipelines', 'workflows', 'builds', 'jobs', 'trigger a pipeline') and no file extensions or synonyms.

3 / 5

Distinctiveness Conflict Risk

Clearly scoped to CircleCI with a distinct trigger, so minimal conflict risk with other skills; only minor overlap risk with generic CI/CD integrations keeps it just below 5.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-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.