recipe-create-shared-drive
Create a Google Shared Drive and add members with appropriate roles.
Profile →npx skills add googleworkspace/cli --skill recipe-create-shared-drive --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Create and Configure a Shared Drive > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-drive` Create a Google Shared Drive and add members with appropriate roles. ## Steps 1. Create shared drive: `gws drive drives create --params '{"requestId": "unique-id-123"}' --json '{"name": "Project X"}'` 2. Add a member: `gws drive permissions create --params '{"fileId": "DRIVE_ID", "supportsAllDrives": true}' --json '{"role": "writer", "type": "user", "emailAddress": "member@company.com"}'` 3. List members: `gws drive permissions list --params '{"fileId": "DRIVE_ID", "supportsAllDrives": true}'`
- Steps
What does the recipe-create-shared-drive skill do?
Create a Google Shared Drive and add members with appropriate roles.
How do I install it?
Run `npx skills add googleworkspace/cli --skill recipe-create-shared-drive --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From googleworkspace/cli, a repository with 30,193 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.