recipe-create-shared-drive
Create a Google Shared Drive and add members with appropriate roles.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-create-shared-drive65
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 Google product and two concrete actions, providing moderate specificity. However, it lacks explicit trigger guidance ('Use when...') which is critical for skill selection, and misses common user terminology variations. The description would benefit from expanded trigger terms and clear usage conditions.
Suggestions
Add a 'Use when...' clause with trigger terms like 'create shared drive', 'team drive', 'add collaborators', 'share Google Drive folder', or 'manage drive permissions'
Include common terminology variations such as 'team drive' (legacy term), 'shared folder', 'Google Workspace', and 'drive access'
Expand the capability list to include related actions like listing existing drives, modifying member roles, or removing access if applicable
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Shared Drive) and two actions (create, add members with roles), but not comprehensive - doesn't mention other potential capabilities like removing members, modifying permissions, or listing drives. | 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 'Use when' caps completeness at 2, and this is missing entirely. | 1 / 3 |
Trigger Term Quality | Includes 'Google Shared Drive' and 'members' which are relevant keywords, but missing common variations like 'team drive', 'shared folder', 'Google Drive permissions', 'add collaborators', or 'share access'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to Google Shared Drives which helps distinguish it, but could overlap with general Google Drive skills, file sharing skills, or permission management skills without clearer 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 immediately actionable commands for creating and configuring a Shared Drive. The main weakness is the lack of validation steps between operations - particularly important since step 2 depends on the DRIVE_ID from step 1, and there's no explicit guidance on capturing or verifying that ID.
Suggestions
Add explicit guidance on capturing the DRIVE_ID from step 1's response before proceeding to step 2
Include a validation step after drive creation to confirm success before adding members
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient with no unnecessary explanations. Every line serves a purpose - prerequisite, description, and executable commands. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands with specific parameters and JSON payloads. Clear placeholders (DRIVE_ID) indicate where customization is needed. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (create -> add member -> list), but lacks validation checkpoints. No guidance on verifying the drive was created successfully before adding members, or error handling if permission creation fails. | 2 / 3 |
Progressive Disclosure | For this simple, single-purpose skill under 50 lines, the structure is appropriate. Clear prerequisite reference to external skill, concise steps, no need for additional file references. | 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.