recipe-save-email-to-doc
Save a Gmail message body into a Google Doc for archival or reference.
71
65%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-save-email-to-doc/SKILL.mdQuality
Discovery
57%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 clearly identifies a specific cross-service workflow (Gmail to Google Docs) which gives it good distinctiveness, but it is limited to a single action and lacks an explicit 'Use when...' clause. Adding trigger terms covering common user phrasings (e.g., 'email', 'backup', 'export') and an explicit usage trigger would significantly improve skill selection accuracy.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to save, export, or back up an email from Gmail into Google Docs.'
Include common trigger term variations such as 'email', 'backup email', 'export Gmail', 'save email to doc' to improve matching against natural user language.
Consider listing additional concrete actions if applicable, such as formatting preservation or handling attachments, to increase specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gmail, Google Doc) and a specific action (save message body), but describes only a single action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Clearly answers 'what' (save Gmail message body into a Google Doc) and hints at 'why' (archival or reference), but lacks an explicit 'Use when...' clause with trigger guidance, which caps this at 2. | 2 / 3 |
Trigger Term Quality | Includes natural keywords like 'Gmail', 'Google Doc', 'message body', and 'archival', but misses common variations users might say such as 'email', 'save email', 'export email', 'backup', or 'Google Docs'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Gmail-to-Google-Doc is a very specific niche workflow that is unlikely to conflict with other skills; the integration between two specific Google services creates a clear, distinct trigger. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, well-structured recipe that clearly outlines the workflow for saving a Gmail message to Google Docs. Its main weaknesses are the lack of guidance on passing data between steps (extracting MSG_ID from step 1's output, extracting email body from step 2's output) and the absence of any validation or error handling checkpoints.
Suggestions
Add brief notes on how to extract MSG_ID from the list response and DOC_ID from the create response to chain the steps together.
Add a validation step after step 1 (e.g., 'Verify the message was found before proceeding') and after step 4 (e.g., 'Confirm the doc content was written successfully').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. The prerequisite note is necessary, and every line serves a purpose with no unnecessary explanation of what Gmail or Google Docs are. | 3 / 3 |
Actionability | Commands are concrete and specific, but they use placeholders like MSG_ID, DOC_ID, and [EMAIL BODY] without explaining how to extract and pass these values between steps. The email body extraction from the JSON response and insertion into the next command is left implicit. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced and numbered, but there are no validation checkpoints—no verification that the message was found, that the doc was created successfully, or that the content was written correctly. There's also no error handling guidance if the search returns no results. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines, the structure is appropriate. It references prerequisite skills clearly and keeps the content well-organized without needing external files. | 3 / 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 |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
a3768d0
- 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.