recipe-create-shared-drive
Create a Google Shared Drive and add members with appropriate roles.
74
68%
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-create-shared-drive/SKILL.mdQuality
Discovery
50%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 specific about what it does (creating Google Shared Drives and adding members) and occupies a clear niche, but it critically lacks any 'Use when...' guidance to help Claude know when to select this skill. Adding trigger terms and common user phrasings would significantly improve its effectiveness in a multi-skill selection context.
Suggestions
Add a 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks to create a shared drive, set up a team drive, or manage shared drive membership in Google Workspace.'
Include common keyword variations users might say, such as 'team drive', 'Google Workspace', 'drive permissions', 'shared folder', or 'collaborators'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists two specific concrete actions: 'Create a Google Shared Drive' and 'add members with appropriate roles.' These are clear, actionable capabilities. | 3 / 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, 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 good natural keywords like 'Google Shared Drive', 'add members', and 'roles', but misses common variations users might say such as 'team drive', 'shared folder', 'permissions', 'collaborators', or 'Google Drive sharing'. | 2 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche—Google Shared Drive creation and member management—which is unlikely to conflict with other skills. The combination of 'Google Shared Drive' + 'add members' + 'roles' 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 concise, actionable skill that provides concrete CLI commands for creating and configuring a Google Shared Drive. Its main weakness is the lack of validation steps between operations—there's no check that the drive was successfully created before adding members, and no guidance on handling errors or verifying the final state. The prerequisite callout and lean structure are strengths.
Suggestions
Add a validation step after drive creation to confirm the DRIVE_ID was returned successfully before proceeding to add members (e.g., capture the output and verify the drive ID exists).
Add a verification step at the end to confirm members were added with the correct roles, such as checking the output of the permissions list command.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Shared Drives are or how Google Workspace works. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully concrete, copy-paste ready CLI commands with specific parameter structures and JSON payloads. The commands are executable with only placeholder substitution needed. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (create drive → add member → list members), but there are no validation checkpoints. No verification that the drive was created successfully before adding members, no error handling if permission creation fails, and no feedback loop for batch member additions. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with a clear prerequisite callout and a concise step-by-step structure. 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 | |
- 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.