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.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill circleci-automation81
Quality
72%
Does it follow best practices?
Impact
100%
1.44xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/circleci-automation/SKILL.mdDiscovery
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.
This description effectively communicates specific CircleCI automation capabilities and is clearly distinguishable from other skills. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords like 'CI/CD' or 'build status' to improve discoverability.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user asks about CircleCI builds, CI/CD pipelines, or needs to check build status'
Include common user terms like 'CI/CD', 'build', 'deployment status', 'continuous integration' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with specific actions but lacks an explicit 'Use when...' clause. The instruction 'Always search tools first' is operational guidance, not trigger guidance for when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'CircleCI', 'pipelines', 'workflows', 'jobs', 'artifacts' but missing common user variations like 'CI/CD', 'build status', 'deployment', or 'continuous integration'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific to CircleCI via Rube MCP (Composio) - unlikely to conflict with other CI/CD skills due to the explicit platform and integration naming. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%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, actionable skill with clear workflow sequences and concrete tool guidance. The main weakness is some redundancy in pitfall documentation and the content being somewhat verbose for what could be more concise. The hierarchical structure and quick reference table are particularly strong elements.
Suggestions
Consolidate pitfall documentation - remove duplicates from individual workflow sections and keep only the 'Known Pitfalls' section, or vice versa
Consider extracting the Quick Reference table and detailed pitfalls into a separate REFERENCE.md file to reduce main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy - pitfalls are repeated across sections (e.g., project_slug format explained multiple times), and some explanations could be tighter. The 'Known Pitfalls' section duplicates information already covered in individual workflow sections. | 2 / 3 |
Actionability | Provides concrete tool sequences with specific parameter names, clear format examples (project_slug patterns), and explicit step-by-step workflows. The quick reference table and hierarchy pattern are immediately usable. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with numbered steps, prerequisite markers ([Prerequisite], [Required], [Optional]), and explicit tool sequences. The Pipeline -> Workflow -> Job hierarchy is well-documented with clear navigation between entities. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in a single file. For a skill of this length (~180 lines), some content like detailed pitfalls or the quick reference could be split into separate files. However, the structure within the file is logical. | 2 / 3 |
Total | 10 / 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 | |
- 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.