gmail-automation
Automate Gmail tasks via Rube MCP (Composio): send/reply, search, labels, drafts, attachments. Always search tools first for current schemas.
72
Quality
60%
Does it follow best practices?
Impact
96%
1.52xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/gmail-automation/SKILL.mdDiscovery
42%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 effectively lists specific Gmail capabilities but critically lacks explicit trigger guidance ('Use when...') which is essential for skill selection. The technical reference to 'Rube MCP (Composio)' adds implementation context but doesn't help Claude know when to choose this skill. Missing common email-related trigger terms like 'email' or 'inbox' reduces discoverability.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to send emails, manage Gmail inbox, work with email attachments, or automate email workflows.'
Include common email-related trigger terms users would naturally say: 'email', 'mail', 'inbox', 'compose', 'forward'
Move the implementation note ('Always search tools first for current schemas') to the skill body rather than the description, as it's not relevant for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'send/reply, search, labels, drafts, attachments' - these are clear, actionable capabilities for Gmail automation. | 3 / 3 |
Completeness | Describes what it does (Gmail tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The 'Always search tools first' is implementation guidance, not usage triggers. | 1 / 3 |
Trigger Term Quality | Includes 'Gmail' and action terms like 'send', 'reply', 'search', 'labels', 'drafts', 'attachments', but missing common variations users might say like 'email', 'mail', 'inbox', 'compose'. | 2 / 3 |
Distinctiveness Conflict Risk | Specifies 'Gmail' and 'Rube MCP (Composio)' which provides some distinctiveness, but could overlap with other email-related skills. The technical implementation detail helps but doesn't fully prevent conflicts with generic email skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent workflow clarity and specific tool guidance. The main weaknesses are some redundancy in pitfall documentation and the monolithic structure that could benefit from splitting detailed workflows or the quick reference into separate files. The content successfully teaches Gmail automation through clear tool sequences and concrete parameter specifications.
Suggestions
Consolidate duplicate pitfall warnings (ID formats, query syntax) into a single 'Common Pitfalls' section and reference it from workflows instead of repeating
Consider moving the Quick Reference table and Gmail Query Syntax sections to separate reference files, keeping SKILL.md as a concise overview with links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - pitfalls are repeated across sections (e.g., ID format warnings appear multiple times), and some explanations could be tighter. The 'Known Pitfalls' section largely duplicates information already in workflow sections. | 2 / 3 |
Actionability | Excellent actionability with specific tool names, exact parameter names, concrete examples of query syntax, and clear tool sequences for each workflow. The quick reference table and ID resolution patterns provide copy-paste ready guidance. | 3 / 3 |
Workflow Clarity | Each workflow has clear numbered tool sequences with [Required], [Optional], and [Prerequisite] annotations. Validation steps are implicit but appropriate (e.g., 'Confirm connection status shows ACTIVE before running any workflows'). The tool sequences clearly show dependencies. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document that could benefit from splitting detailed workflows into separate files. The external link to Composio docs is good, but all 300+ lines are inline rather than using progressive disclosure to separate reference material. | 2 / 3 |
Total | 10 / 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.