Save a Gmail message body into a Google Doc for archival or reference.
77
72%
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 is concise and identifies a clear, specific workflow (Gmail to Google Doc), giving it good distinctiveness. However, it lacks an explicit 'Use when...' clause and misses common user trigger terms like 'email', 'export', or 'backup', which limits its effectiveness for skill selection among many options.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to save, export, or archive an email from Gmail into a Google Doc.'
Include common trigger term variations such as 'email', 'export email', 'backup email', 'copy email to Google Docs', and 'save email content'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Describes a specific action ('Save a Gmail message body into a Google Doc') with a clear domain, but only names one concrete action rather than listing multiple 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 for when Claude should select this skill. | 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', 'copy email to doc', or 'backup email'. | 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 cross-service integration (Gmail + Google Docs) creates a distinct trigger profile. | 3 / 3 |
Total | 9 / 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 recipe skill that provides clear, actionable CLI commands in a logical sequence. Its main weakness is the lack of any validation or error-handling guidance between steps — e.g., confirming the message was found before proceeding, or verifying the doc was created before writing to it.
Suggestions
Add a brief validation note after step 1 (e.g., 'Confirm the message ID appears in results before proceeding') and after step 3 (e.g., 'Note the returned document ID for the next step').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. No unnecessary explanations of what Gmail or Google Docs are. Every line serves a purpose, and the prerequisite is stated concisely. | 3 / 3 |
Actionability | Provides fully concrete, copy-paste ready CLI commands for each step with realistic parameters and placeholders (MSG_ID, DOC_ID). The commands are specific and executable. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and logical, 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. For a multi-step workflow involving data transfer, some validation would be appropriate. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines with a single task, the content is well-organized with a clear prerequisite callout and numbered steps. No need for external references given the scope. | 3 / 3 |
Total | 11 / 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 | |
c7c6646
Table of Contents
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.