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

65%

Does it follow best practices?

Impact

100%

1.44x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/circleci-automation/SKILL.md

Quality

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 concise and specific about its capabilities, clearly naming the platform (CircleCI) and the integration tool (Rube MCP/Composio) along with concrete actions. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Adding more natural user trigger terms related to CI/CD would also improve discoverability.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about CircleCI builds, pipeline status, CI/CD workflows, or retrieving build artifacts.'

Include common user-facing trigger terms like 'CI/CD', 'build status', 'build logs', 'continuous integration', or 'deployment pipeline' to improve matching against natural user queries.

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' (automate CircleCI tasks via Rube MCP), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the capability listing, which per the rubric should cap completeness at 2.	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	Very distinct niche: CircleCI automation via a specific MCP tool (Rube/Composio). The combination of the platform (CircleCI) and the integration method (Rube MCP/Composio) makes it highly 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 skill with excellent workflow clarity and good structural organization. Its main weaknesses are redundancy across sections (project slug format and ID types repeated multiple times) and lack of concrete executable examples showing actual tool invocations with filled-in parameters. The content would benefit from deduplication and adding at least one complete worked example.

Suggestions

Add a concrete worked example showing an actual tool invocation with real parameter values (e.g., a complete CIRCLECI_TRIGGER_PIPELINE call with a sample project_slug, branch, and parameters)

Consolidate repeated pitfalls (project_slug format, ID types) into the 'Known Pitfalls' section only, and reference that section from the individual workflows instead of restating

Consider moving the detailed per-workflow sections into a separate reference file, keeping SKILL.md as a concise overview with the quick reference table and setup instructions

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-structured but has notable redundancy. Pitfalls about project_slug format and ID types are repeated across multiple sections and again in the 'Known Pitfalls' section. The 'Pipeline -> Workflow -> Job Hierarchy' pattern repeats what's already covered in the core workflows. Some trimming would improve token efficiency.	2 / 3
Actionability	The skill provides specific tool names, parameter names, and tool sequences, which is good. However, there are no executable code examples or concrete invocation snippets showing actual tool calls with example parameters filled in. The guidance is specific but stops short of copy-paste ready examples.	2 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with numbered steps, prerequisite/required/optional annotations, and explicit tool ordering. The setup section includes a verification step before proceeding. The hierarchy of pipeline -> workflow -> job is well-documented with clear navigation between levels.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and a quick reference table, but it's quite long (~150+ lines of substantive content) and could benefit from splitting detailed workflow descriptions or pitfalls into separate reference files. The external link to Composio docs is present but the skill itself is somewhat monolithic.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 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: Lingjie-chen/MT5
Commit: 3069d33

Reviewed: 26 days 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.