recipe-search-and-export-emails
Find Gmail messages matching a query and export them for review.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-search-and-export-emails65
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/skillValidation for skill structure
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 identifies a clear domain (Gmail) and basic functionality but suffers from missing explicit trigger guidance and limited keyword coverage. It would benefit significantly from a 'Use when...' clause and additional natural terms users might use when needing this skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'search Gmail', 'find emails', 'export messages', 'email search'
Include common variations users might say: 'email', 'inbox', 'search emails', 'download emails'
Specify what 'export for review' means - formats, destinations, or review capabilities
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gmail) and two actions (find messages, export for review), but lacks comprehensive detail about what 'export' means or what formats/capabilities are available. | 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', 'search emails', 'download messages', or 'inbox'. | 2 / 3 |
Distinctiveness Conflict Risk | Gmail-specific which helps distinguish from generic document skills, but could overlap with other email-related skills; lacks explicit triggers to clarify its niche. | 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 that provides immediately actionable commands for searching and exporting Gmail messages. Its main weakness is the lack of validation or error handling guidance—users aren't told how to handle pagination, empty results, or API errors, which could be important for batch export operations.
Suggestions
Add a note about handling pagination when search returns many results (nextPageToken)
Include a brief validation step or expected output format so users can verify the export succeeded
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations, assumes Claude knows what Gmail and JSON are. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable CLI commands with realistic example parameters. Copy-paste ready with clear placeholders (MSG_ID) where user input is needed. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (search → get → export), but lacks validation checkpoints. No guidance on handling empty results, pagination for large result sets, or error scenarios. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the structure is appropriate. Clear prerequisite callout, concise steps, no need for external references. | 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 | |
- 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.