CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-mail-automation

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

72

2.42x
Quality

58%

Does it follow best practices?

Impact

97%

2.42x

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/agent-mail-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 concise, actionable single-file guide with concrete MCP call examples and a clear sequenced workflow. Its main weakness is the lack of an explicit execution-result verification and error-recovery feedback loop for batch operations, which caps workflow clarity.

Suggestions

Add a post-execution validation step to the Core Workflow (e.g. inspect RUBE_MULTI_EXECUTE_TOOL results for errors, retry failed tools, and confirm pagination is exhausted before declaring success).

Consolidate the repeated "Always search tools first" guidance into a single Prerequisite statement to remove redundancy.

Show one fully-resolved worked example with real-looking tool slugs and arguments so users see a complete end-to-end call chain.

DimensionReasoningScore

Conciseness

The body is lean and code-block-driven without explaining concepts Claude already knows; the only redundancy is "Always search tools first" repeated across Prerequisites, Step 1, and Known Pitfalls, which is minor over-explanation that could be trimmed.

4 / 5

Actionability

Concrete RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL call blocks with example arguments are mostly executable; placeholders like TOOL_SLUG_FROM_SEARCH are justified by the schema-drift caveat, leaving only minor gaps.

4 / 5

Workflow Clarity

A clear Step 1-2-3 sequence exists with a pre-execution connection check, but the workflow involves batch operations (RUBE_MULTI_EXECUTE_TOOL, RUBE_REMOTE_WORKBENCH bulk ops) with no explicit validate→fix→retry feedback loop, so per the batch-operations cap workflow clarity stays at 3.

3 / 5

Progressive Disclosure

No bundle files exist and none are needed since schemas come from the live MCP; the single self-contained file is well organized into Setup, Tool Discovery, Core Workflow, Pitfalls, and Quick Reference, fitting good structure with only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

48%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 names a specific, distinctive toolkit and integration but uses a generic verb ("Automate tasks") and omits any "Use when..." trigger guidance. Adding concrete capabilities and an explicit use-when clause would lift completeness and specificity.

Suggestions

Replace the generic verb with concrete capabilities, e.g. "Send, read, and manage Agent Mail messages and threads via Rube MCP (Composio)."

Add an explicit "Use when..." clause, e.g. "Use when the user needs to send or automate Agent Mail messages."

Include natural trigger synonyms users might say (e.g. "Agent Mail messages", "Agent Mail automation") alongside the product names.

DimensionReasoningScore

Specificity

"Automate Agent Mail tasks via Rube MCP" names the domain and integration but the action ("Automate ... tasks") is generic, matching the score-2 anchor of naming a domain with minimal/generic actions rather than concrete capabilities.

2 / 5

Completeness

It states a clear "what" (automate Agent Mail via Rube MCP) but provides no "Use when..." trigger guidance, so per the judging guidelines completeness is capped at 3 for a clear what with missing when.

3 / 5

Trigger Term Quality

"Agent Mail" is a relevant keyword a user might say, but surrounding terms ("Rube MCP", "Composio", "current schemas") are product/technical jargon with no natural synonyms or variations, fitting the score-3 anchor of some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

"Agent Mail" is a specific named Composio toolkit giving it a clear niche with minimal conflict risk, though the brevity and generic verb keep it just short of the fully-distinct score-5 anchor.

4 / 5

Total

12

/

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.