recipe-email-drive-link
Share a Google Drive file and email the link with a message to recipients.
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-email-drive-link/SKILL.mdQuality
Discovery
42%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 states what the skill does with concrete actions (share, email, link), which is a strength. However, it lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill from a pool of many. The trigger terms are decent but could be expanded to cover more natural user phrasings.
Suggestions
Add a 'Use when...' clause such as 'Use when the user wants to share a Google Drive file via email, send a Drive link, or grant access to a document and notify recipients.'
Include additional trigger terms and variations like 'Google Docs', 'Google Sheets', 'send file link', 'share document', 'grant access', or 'collaborate' to improve matching.
Clarify the scope to distinguish from general email or general Google Drive skills, e.g., specify that this skill handles both the sharing permission change and the email notification in one workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists specific concrete actions: sharing a Google Drive file, emailing the link, and including a message to recipients. These are clear, actionable capabilities. | 3 / 3 |
Completeness | The description answers 'what does this do' but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes natural keywords like 'Google Drive', 'share', 'email', and 'link', but misses common variations users might say such as 'send a file', 'share link via email', 'Google Docs', 'permissions', or 'collaborate'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Google Drive sharing and emailing is somewhat specific, but could overlap with general email skills or general Google Drive management skills. The description doesn't clearly delineate its niche from those adjacent capabilities. | 2 / 3 |
Total | 8 / 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 with concrete, executable commands and a clear three-step workflow. Its main weakness is the lack of validation checkpoints between steps — particularly verifying the file was found before sharing and confirming the permission was created before emailing the link.
Suggestions
Add a brief validation note after step 1 (e.g., 'Confirm the file ID is returned before proceeding') and after step 2 (e.g., 'Verify the permission was created successfully') to prevent errors from cascading.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Google Drive or Gmail are. Every line serves a purpose — prerequisite, description, and concrete steps. | 3 / 3 |
Actionability | Provides fully concrete, copy-paste-ready CLI commands with realistic parameters, placeholders (FILE_ID), and example values. Each step is directly executable. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and logical (find → share → email), but there are no validation checkpoints — e.g., no verification that the file was found, that the permission was successfully created, or that the email was sent. Sharing is a potentially impactful operation that would benefit from a confirmation step. | 2 / 3 |
Progressive Disclosure | For a simple, short recipe skill under 50 lines, the structure is appropriate. It references prerequisite skills clearly and keeps the content self-contained without unnecessary nesting or monolithic blocks. | 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 | |
- Repository
- googleworkspace/cli
- Commit
c7c6646
- 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.