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.
76
65%
Does it follow best practices?
Impact
100%
1.44xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/circleci-automation/SKILL.mdQuality
Discovery
67%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 strong in specificity and distinctiveness, clearly listing concrete CircleCI automation actions and naming the specific tooling (Rube MCP/Composio). However, it lacks an explicit 'Use when...' clause which caps completeness, and the trigger terms lean toward technical jargon rather than natural user language variations.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about CircleCI builds, CI/CD pipelines, build status, or deployment workflows.'
Include more natural user-facing trigger terms like 'CI/CD', 'build status', 'continuous integration', 'deployment', or 'build logs' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata.' Also includes a procedural instruction ('Always search tools first for current schemas'). | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain context. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'CircleCI', 'pipelines', 'workflows', 'jobs', 'artifacts', and 'test metadata', but misses common user variations like 'CI/CD', 'build status', 'deployment', or 'continuous integration'. 'Rube MCP (Composio)' is internal jargon unlikely to be used by users. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of 'CircleCI', 'Rube MCP (Composio)', and CI/CD-specific actions like triggering pipelines and retrieving artifacts. Unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference skill for CircleCI automation via Rube MCP with clear workflow sequences and good structural organization. Its main weaknesses are redundancy across sections (pitfalls and patterns repeated multiple times) and the lack of concrete executable examples showing actual MCP tool call syntax. The workflow clarity is strong with explicit sequencing and prerequisite annotations.
Suggestions
Deduplicate repeated information: consolidate project_slug format, ID type warnings, and pagination guidance into single authoritative sections rather than repeating across workflows and 'Known Pitfalls'.
Add at least one concrete, executable MCP tool call example showing the exact invocation syntax (e.g., a complete RUBE_SEARCH_TOOLS call followed by CIRCLECI_TRIGGER_PIPELINE with real parameter values).
Consider extracting the detailed per-workflow pitfalls and the quick reference table into a separate REFERENCE.md to keep SKILL.md leaner as an overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but has notable redundancy. Pitfalls about project_slug format, ID types (UUIDs vs integers), and pagination are repeated across multiple sections and then again in 'Known Pitfalls' and 'Common Patterns'. The 'Pipeline -> Workflow -> Job Hierarchy' pattern repeats what's already shown in the core workflows. Some trimming would improve token efficiency. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and clear tool sequences, which is good. However, there are no executable code examples or concrete MCP call syntax showing exact invocation patterns. The guidance is specific enough to follow but stops short of copy-paste ready examples with actual tool call formats. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with explicit prerequisite/required/optional annotations. Each workflow has a clear 'when to use' trigger, ordered tool sequence, key parameters, and pitfalls. The setup section includes a validation checkpoint (confirm ACTIVE status before proceeding). The hierarchy pattern clearly shows the drill-down sequence. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a quick reference table, but it's a monolithic document with significant content that could be split out (e.g., the detailed pitfalls, common patterns). There are no bundle files to reference, and the single external link is to Composio docs. For a skill of this length (~150+ lines), some content could benefit from being in separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
74c7031
- 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.