circleci-automation

Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas.

1.44x

Quality

73%

Does it follow best practices?

Impact

100%

1.44x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/circleci-automation/SKILL.md

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.

The content is a well-structured, actionable reference for orchestrating CircleCI via Rube MCP, with clear sequenced workflows and concrete tool/parameter guidance. The main room for improvement is reducing cross-section redundancy and adding explicit post-trigger validation checkpoints.

Suggestions

Consolidate the repeated project-slug and ID-format guidance into the 'Common Patterns'/'Known Pitfalls' sections and reference them from individual workflows to reduce redundancy.

Add an explicit validation/feedback step after triggering a pipeline (e.g., poll CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID until the pipeline reaches a terminal state) to strengthen workflow clarity.

Consider extracting the per-workflow detailed pitfalls or the Quick Reference table into a reference file to move progressive disclosure toward a 5.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanation of what CI/CD or a pipeline is), but project-slug format and ID-format pitfalls recur across multiple workflow sections and the 'Known Pitfalls' summary, which is minor redundant padding.	4 / 5
Actionability	Provides concrete, executable guidance via specific tool slugs (e.g., CIRCLECI_TRIGGER_PIPELINE), exact parameter formats (gh/org/repo), and per-workflow pitfalls; it stops short of fully copy-paste-ready literal code, which is appropriate for MCP tool orchestration.	4 / 5
Workflow Clarity	Multi-step workflows are clearly sequenced with numbered tool calls, 'When to use' context, and prerequisite checkpoints (e.g., 'Confirm job completed successfully' before fetching artifacts); minor validation gaps remain, such as no explicit verify-state step after triggering a pipeline.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is self-contained with well-organized sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) providing easy navigation; at ~175 lines all content is inline, which is reasonable for an MCP orchestration skill but lacks the one-level-deep references that would warrant a 5.	4 / 5
	Total	16 / 20 Passed

Description

71%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 specific and distinct, naming concrete CircleCI actions and a clear integration target. Its main weakness is the missing explicit 'Use when...' trigger guidance, which limits completeness and slightly weakens trigger-term quality and distinctiveness.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user wants to trigger or monitor CircleCI pipelines, inspect job/artifact/test results, or manage CI/CD runs') to raise completeness above 3.

Include common synonyms users say ('CI/CD runs', 'builds', 'deployments') to broaden trigger-term coverage.

Keep the third-person voice and concrete action list as-is; they are already strong.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata' — giving comprehensive coverage of the skill's capabilities, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	The 'what' is clear (automate CircleCI tasks with enumerated actions) but there is no explicit 'Use when...' trigger clause — only procedural guidance ('Always search tools first') — so per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Strong natural keywords ('CircleCI', 'pipelines', 'workflows', 'jobs', 'artifacts', 'test metadata', 'trigger', 'monitor') that users would say, but missing synonyms like 'CI/CD', 'builds', or 'deployments' that prevent a fully comprehensive score.	4 / 5
Distinctiveness Conflict Risk	Names a specific product and integration ('CircleCI tasks via Rube MCP (Composio)'), giving a clear niche with minimal conflict risk, but the absence of explicit trigger phrases leaves minor overlap risk with general CI/CD or Composio skills.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/circleci-automation/SKILL.md
Commit: a9fa86d

Reviewed: about 20 hours ago

Table of Contents

Discovery Implementation Validation

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.