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 naming the tool ecosystem (CircleCI via Rube MCP/Composio) and listing concrete actions. Its main weaknesses are the lack of an explicit 'Use when...' clause and missing some natural trigger terms users might employ when requesting CI/CD help.
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 additional natural trigger terms like 'CI/CD', 'build status', 'build logs', 'continuous integration', or 'deployment' 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 capability listing, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'CircleCI', 'pipelines', 'workflows', 'jobs', 'artifacts', 'test metadata', and 'Rube MCP (Composio)'. However, it misses common user variations like 'CI/CD', 'build status', 'deployment', 'continuous integration', or 'build logs' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'CircleCI' and 'Rube MCP (Composio)'. This is a clear niche that is unlikely to conflict with other skills unless there are multiple CircleCI-related 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 with clear workflow sequences and good structural annotations (prerequisite/required/optional). Its main weaknesses are redundancy across sections (pitfalls and patterns repeated multiple times) and lack of concrete executable examples showing actual MCP tool call syntax. The content would benefit from deduplication and adding at least one complete worked example.
Suggestions
Deduplicate repeated information: project_slug format, ID type distinctions, and pagination are each explained 2-3 times across different sections. Consolidate into the 'Known Pitfalls' and 'Common Patterns' sections and reference them from workflows.
Add at least one concrete, executable example showing the actual MCP tool call syntax (e.g., a complete RUBE_SEARCH_TOOLS call followed by CIRCLECI_TRIGGER_PIPELINE with real parameter values) to move from descriptive to copy-paste actionable.
Consider splitting the Quick Reference table and Known Pitfalls into a separate REFERENCE.md file to reduce the main skill's token footprint and improve progressive disclosure.
| 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 duplicates what's already shown in the workflow sections. 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 file with no bundle files to offload detailed content. The repeated pitfalls and common patterns sections could be split into separate reference files. For a skill of this length (~150+ lines), some content like the full pitfalls catalog and quick reference table would benefit from being in separate 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
d065ead
- 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.