recipe-save-email-to-doc
Save a Gmail message body into a Google Doc for archival or reference.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-save-email-to-doc65
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 integration between Gmail and Google Docs but is too narrow in scope (single action) and critically lacks explicit trigger guidance. It would benefit from additional trigger terms covering common user phrasings and a 'Use when...' clause to help Claude distinguish this skill from other email or document-related skills.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to save, export, or archive an email to Google Docs'
Include natural keyword variations users would say: 'email', 'save email', 'export message', 'backup email', 'copy to Google Docs'
Consider expanding capabilities or clarifying scope: does it handle attachments, multiple emails, or formatting preservation?
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gmail, Google Doc) and describes one specific action (save message body for archival/reference), but only covers a single capability rather than listing multiple concrete actions. | 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. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'when' is entirely absent, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Gmail', 'message body', 'Google Doc', 'archival', but missing common variations users might say like 'email', 'save email', 'export', 'backup', or 'copy to docs'. | 2 / 3 |
Distinctiveness Conflict Risk | The Gmail-to-Google-Doc pipeline is somewhat specific, but could overlap with general email skills, document creation skills, or other Google Workspace integration skills without clearer trigger boundaries. | 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 clear, actionable commands for a straightforward workflow. The main weakness is the lack of validation steps between operations - there's no guidance on verifying the message was found or confirming the document was created before writing to it.
Suggestions
Add a validation note after step 1 to verify a message was found before proceeding (e.g., 'Confirm the message ID exists in the response')
Include a brief verification step after step 3 to confirm the document was created successfully before writing content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only the essential commands without explaining what Gmail or Google Docs are. Every line serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable CLI commands with realistic examples including query syntax, parameter formats, and placeholder values. Commands are copy-paste ready with clear substitution points (MSG_ID, DOC_ID). | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and numbered, but lacks validation checkpoints. No verification that the message was found, that the doc was created successfully, or that the content was written correctly before proceeding. | 2 / 3 |
Progressive Disclosure | For this simple 4-step recipe under 50 lines, the structure is appropriate. The prerequisite skills are clearly referenced at the top, and the content is well-organized without needing external files. | 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.