recipe-email-drive-link
Share a Google Drive file and email the link with a message to recipients.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-email-drive-link65
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 specific workflow (sharing Google Drive files via email) but lacks the explicit trigger guidance needed for Claude to reliably select it from a large skill library. The 'what' is adequately specific but not comprehensive, and the absence of a 'Use when...' clause significantly weakens its utility for skill selection.
Suggestions
Add a 'Use when...' clause with trigger terms like 'share Google Drive', 'send Drive link', 'email a file from Drive', 'grant access to document'
Expand the capability description to include specifics like permission types (view, edit, comment), handling multiple recipients, or customizing sharing settings
Include natural language variations users might say: 'share my doc', 'send someone access', 'give them the link'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Drive) and describes actions (share file, email link with message), but lacks comprehensive detail about specific capabilities like permission levels, multiple recipients handling, or attachment options. | 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 'what' is also minimal, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Google Drive', 'share', 'email', and 'link', but misses common variations users might say like 'send a file', 'share access', 'Drive link', or 'grant permissions'. | 2 / 3 |
Distinctiveness Conflict Risk | Combines Google Drive sharing with email, which provides some distinctiveness, but could overlap with general email skills or other file-sharing skills. The combination helps but isn't fully distinct. | 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 recipe skill that provides clear, executable commands for a straightforward 3-step workflow. Its main weakness is the lack of validation steps between operations—there's no verification that the file search returned results or that the permission was successfully created before proceeding to email.
Suggestions
Add a validation step after file search to confirm the file was found before proceeding (e.g., check response contains fileId)
Consider adding a verification step after permission creation to confirm sharing succeeded before emailing the link
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations, assumes Claude knows what Google Drive and Gmail are, every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable CLI commands with concrete examples including parameter syntax, JSON payloads, and placeholder values that are clearly marked (FILE_ID). | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (find → share → email), but lacks validation checkpoints. No verification that the file was found, that sharing succeeded, or that the email was sent. For operations involving sharing permissions, validation would be valuable. | 2 / 3 |
Progressive Disclosure | Appropriate for a simple recipe skill. Clear prerequisite reference to dependent skills, well-organized single-level structure, no unnecessary nesting or monolithic content. | 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.