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 a Google Shared Drive and adding members) and occupies a clear niche, but it completely lacks trigger guidance ('Use when...') which is critical for Claude to know when to select this skill. It also misses common user-facing synonyms like 'team drive' or 'permissions'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create a shared drive, set up a team drive, or manage shared drive membership.'
Include common trigger term variations such as 'team drive', 'permissions', 'collaborators', 'Google Drive sharing', or 'shared folder' to improve keyword coverage.
| 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' and 'add members with roles' is quite distinctive. | 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.
A concise, actionable skill that provides concrete CLI commands for creating a Shared Drive and managing members. Its main weakness is the workflow gap around capturing the DRIVE_ID from step 1 and using it in subsequent steps, plus the lack of any validation or error recovery guidance.
Suggestions
Add an explicit step after drive creation to capture the DRIVE_ID from the response output, e.g., 'Note the `id` field from the response to use as DRIVE_ID in subsequent steps'.
Add a verification step after adding members, such as confirming the permissions list output includes the expected member with the correct role.
| 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 for each step. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (create → add member → list members), but there's no validation checkpoint after drive creation to capture the DRIVE_ID, no error handling if creation fails, and no verification that members were successfully added. The placeholder 'DRIVE_ID' is used without explicit instruction to capture it from step 1's output. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines with a single focused task, the structure is appropriate. The prerequisite skill reference is clearly signaled at the top, and content is well-organized with a clear header and numbered steps. | 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 | |
a3768d0
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.