CtrlK
BlogDocsLog inGet started
Tessl Logo

autom-automation

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

62

Quality

46%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/autom-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

7%

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 is poorly written with unclear terminology ('Autom' appears to be a typo), no concrete actions listed, and no guidance on when to use the skill. The technical jargon (Rube MCP, Composio) won't help Claude match user requests, and the procedural note about searching tools doesn't belong in a description field.

Suggestions

Replace 'Automate Autom tasks' with specific actions this skill can perform (e.g., 'Create workflows, trigger automations, manage integrations')

Add a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about workflow automation, Composio integrations, or connecting apps')

Fix the apparent typo 'Autom' and clarify what domain or platform this skill targets

DimensionReasoningScore

Specificity

The description uses vague language like 'Automate Autom tasks' without explaining what specific actions can be performed. 'Always search tools first' is procedural guidance, not a capability description.

1 / 3

Completeness

The 'what' is extremely vague ('Automate Autom tasks') and there is no 'when' clause or explicit trigger guidance. Both components are weak or missing.

1 / 3

Trigger Term Quality

'Autom' appears to be a typo or unclear term, 'Rube MCP' and 'Composio' are technical jargon that users would not naturally say. No common user-facing keywords are included.

1 / 3

Distinctiveness Conflict Risk

The mention of 'Rube MCP (Composio)' provides some specificity to a particular tool/integration, which helps distinguish it, but 'Automate tasks' is generic enough to potentially conflict with other automation skills.

2 / 3

Total

5

/

12

Passed

Implementation

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill that efficiently guides Claude through Autom automation via Rube MCP. The workflow is clear with proper validation checkpoints, and the content is appropriately concise. The main weakness is that tool call examples use placeholder syntax rather than fully concrete, executable examples.

Suggestions

Replace placeholder comments like '/* schema-compliant args from search results */' with a concrete example showing actual field names and values for a common Autom operation

Add a complete end-to-end example showing a real Autom task from discovery through execution with actual tool slugs and arguments

DimensionReasoningScore

Conciseness

The content is lean and efficient, avoiding unnecessary explanations of what Rube MCP or Composio are. Every section serves a purpose and assumes Claude understands the concepts.

3 / 3

Actionability

Provides concrete tool call patterns with parameter examples, but uses pseudo-code style rather than fully executable examples. The argument placeholders like '/* schema-compliant args */' reduce copy-paste readiness.

2 / 3

Workflow Clarity

Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status and explicit guidance to confirm ACTIVE status before proceeding.

3 / 3

Progressive Disclosure

Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. Quick reference table provides scannable summary. External toolkit docs linked appropriately without deep nesting.

3 / 3

Total

11

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.