CtrlK
BlogDocsLog inGet started
Tessl Logo

agiled-automation

Automate Agiled tasks via Rube MCP (Composio). Always search tools first for current schemas.

73

4.00x
Quality

63%

Does it follow best practices?

Impact

92%

4.00x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/agiled-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 body is a lean, well-structured operational guide with concrete tool-call examples and a sensible setup-to-execute sequence. Its main weakness is the absence of result verification and error-recovery loops for the batch/bulk operations it explicitly enables, which caps workflow clarity.

Suggestions

Add a post-execution verification step and an error-recovery feedback loop (check tool response status/errors -> fix args -> re-run via RUBE_SEARCH_TOOLS) for batch and bulk operations.

Replace placeholder-laden examples (your_session_id, TOOL_SLUG_FROM_SEARCH, {/* schema-compliant args */}) with a concrete end-to-end worked example to push actionability to fully copy-paste ready.

De-duplicate the search-first guidance so it lives in one canonical spot rather than recurring across Prerequisites, Tool Discovery, Core Workflow, and Known Pitfalls.

DimensionReasoningScore

Conciseness

The body is lean — commands, steps, pitfalls, and a quick-reference table with no padding about what Agiled or MCP is — but the search-first guidance and RUBE_SEARCH_TOOLS call are repeated across Prerequisites, Tool Discovery, and Core Workflow, which could be tightened.

4 / 5

Actionability

Concrete tool invocations with real parameter structures are shown (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL, etc.), but several examples retain placeholders (your_session_id, TOOL_SLUG_FROM_SEARCH) and an effectively pseudocode arguments block, so they are not fully copy-paste ready.

4 / 5

Workflow Clarity

Steps are clearly sequenced (Setup 1-4, Core Workflow 1-3) with a pre-execution ACTIVE-status checkpoint, but the skill explicitly supports batch/bulk operations (RUBE_MULTI_EXECUTE_TOOL, RUBE_REMOTE_WORKBENCH) with no post-execution verification or error-recovery feedback loop, capping workflow clarity at 3.

3 / 5

Progressive Disclosure

The single SKILL.md is well-organized into clear, navigable sections with an external docs link and no nested references, and no bundle files exist to split; it slightly exceeds the under-50-lines simple-skill exception but remains well-structured.

4 / 5

Total

15

/

20

Passed

Description

57%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 clearly scoped to a distinct niche (Agiled via Rube MCP) but is generic about the actual capabilities and lacks an explicit "Use when..." trigger, leaving the when-to-use intent implicit. It reads as a brief technical pointer rather than a trigger-rich skill summary.

Suggestions

Add an explicit "Use when..." clause naming concrete Agiled operations (e.g., invoices, projects, CRM contacts) to lift completeness and trigger coverage.

Enumerate 2-3 specific actions (e.g., 'create and update Agiled invoices, projects, and tasks') instead of the generic 'Automate Agiled tasks'.

Include natural user phrasings such as 'Agiled invoices', 'Agiled projects', or 'Agiled CRM' alongside the technical Rube/Composio terms.

DimensionReasoningScore

Specificity

Names the domain ("Agiled tasks") and one concrete action ("search tools first for current schemas"), but the actions are minimal and not comprehensive — "Automate Agiled tasks" is broad rather than enumerating specific operations.

3 / 5

Completeness

It clearly states what the skill does ("Automate Agiled tasks via Rube MCP") but offers no "Use when..." trigger; "Always search tools first" is a how-to instruction, not a when-to-use clause, so completeness is capped at 3 per the missing-trigger guideline.

3 / 5

Trigger Term Quality

"Agiled" is a product-name keyword a user would naturally say, but the description leans on technical jargon ("Rube MCP", "Composio", "schemas") and omits natural synonym variations users might phrase.

3 / 5

Distinctiveness Conflict Risk

The description is anchored to a specific product ("Agiled") and a specific integration path ("Rube MCP / Composio"), giving it a clear niche with minimal overlap with other skills.

5 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
ComposioHQ/awesome-claude-skills
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.