agent-mail-automation
Automate Agent Mail tasks via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:haniakrim21/everything-claude-code --skill agent-mail-automation67
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 97%
↑ 2.42xAgent success when using this skill
Validation for skill structure
Discovery
17%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 too vague and relies heavily on technical jargon that users wouldn't naturally use. It fails to explain what specific mail tasks can be automated and lacks explicit trigger conditions. The operational instruction about searching tools doesn't help Claude decide when to select this skill.
Suggestions
Add a 'Use when...' clause with natural trigger terms like 'email automation', 'mail tasks', 'inbox management', or 'send automated emails'
Replace 'automate tasks' with specific concrete actions like 'send emails, manage contacts, filter inbox, schedule messages'
Include common user phrases that would trigger this skill, avoiding technical terms like 'Rube MCP' and 'Composio' as primary identifiers
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Agent Mail, Rube MCP, Composio) and mentions 'automate tasks' but doesn't list specific concrete actions like 'send emails', 'manage inbox', or 'filter messages'. | 2 / 3 |
Completeness | The 'what' is vague ('automate tasks') and there's no 'Use when...' clause or explicit trigger guidance. The instruction to 'search tools first' is operational guidance, not a trigger condition. | 1 / 3 |
Trigger Term Quality | Uses technical jargon ('Rube MCP', 'Composio') that users wouldn't naturally say. Missing natural terms like 'email', 'mail automation', 'inbox', or 'messages'. | 1 / 3 |
Distinctiveness Conflict Risk | 'Agent Mail' and 'Rube MCP (Composio)' provide some specificity, but 'automate tasks' is generic and could overlap with other automation skills. The technical terms help distinguish it somewhat. | 2 / 3 |
Total | 6 / 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 Agent Mail automation via Rube MCP. The workflow is clear with appropriate validation checkpoints, and the content respects token budget. The main weakness is that tool call examples use placeholder syntax rather than fully concrete examples with realistic argument values.
Suggestions
Replace placeholder comments like '/* schema-compliant args from search results */' with a concrete example showing actual Agent Mail arguments (e.g., sending an email with specific fields)
Add one complete end-to-end example showing a real Agent Mail task from search through execution with actual response handling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts. Every section serves a purpose with no padding or unnecessary context about what Agent Mail or Composio are. | 3 / 3 |
Actionability | Provides concrete tool call patterns with parameter examples, but uses pseudocode-style blocks rather than fully executable code. The argument placeholders like '/* schema-compliant args from search results */' reduce copy-paste readiness. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint (verify ACTIVE status before executing) and the Known Pitfalls section provides error recovery guidance. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to toolkit docs is one level deep. Quick reference table provides efficient navigation for common operations. | 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.
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.