recipe-batch-reply-to-emails
Find Gmail messages matching a query and send a standard reply to each one.
71
60%
Does it follow best practices?
Impact
97%
16.16xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-batch-reply-to-emails/SKILL.mdQuality
Discovery
32%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 provides a basic understanding of the skill's function (finding and replying to Gmail messages) but lacks explicit trigger guidance, which is critical for skill selection. It would benefit from a 'Use when...' clause and more natural trigger terms that users would actually say when needing this functionality.
Suggestions
Add a 'Use when...' clause with trigger terms like 'auto-reply', 'bulk reply to emails', 'respond to Gmail messages', 'batch email response'
Include common keyword variations: 'email', 'inbox', 'auto-reply', 'mass reply', 'bulk response'
Clarify what 'standard reply' means - is it templated, customizable, or fixed content?
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gmail) and two actions (find messages, send reply), but lacks detail on what 'standard reply' means or additional capabilities like filtering options, batch limits, or reply customization. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Gmail messages' and 'query' which are relevant, but misses common variations users might say like 'email', 'inbox', 'auto-reply', 'bulk reply', or 'mass email response'. | 2 / 3 |
Distinctiveness Conflict Risk | Gmail-specific which helps distinguish from generic email skills, but 'send a standard reply' is vague enough that it could overlap with other email automation or response skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%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-crafted, concise skill recipe with executable commands and clear sequencing. The main weakness is the lack of explicit validation or error handling for batch operations—if one reply fails mid-batch, there's no guidance on recovery or verification that all messages were processed correctly.
Suggestions
Add a validation step to verify reply was sent successfully before marking as read (e.g., check response status)
Include guidance on iterating through multiple messages safely, such as a loop pattern or batch processing approach with error handling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only the necessary commands without explaining what Gmail is or how APIs work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable CLI commands with realistic parameters and examples. Commands are copy-paste ready with clear placeholders (MSG_ID, sender@example.com). | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced for a multi-message batch operation, but lacks validation checkpoints and feedback loops. No guidance on error handling if a reply fails, or how to iterate through multiple messages safely. | 2 / 3 |
Progressive Disclosure | Appropriately simple structure for a short recipe. Clear prerequisite reference to the gws-gmail skill, and content is well-organized without unnecessary nesting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
6ed836c
- 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.