Recipe Create Shared Drive
Stand up a Google Shared Drive for a project and add members with writer roles from the terminal.
Overview
Recipe Create Shared Drive is an agent skill for the Build phase that creates a Google Shared Drive and adds members with appropriate roles via `gws drive` commands.
Install
npx skills add https://github.com/googleworkspace/cli --skill recipe-create-shared-driveWhat is this skill?
- 3-step recipe: drives create with requestId, add member as writer, list permissions
- `supportsAllDrives: true` on permission list and create for shared drive scope
- Prerequisite skill `gws-drive` only (single domain dependency)
- requestId must be unique for idempotent drive creation
- Lists members after add for verification
- metadata version 0.22.5
Adoption & trust: 15.6k installs on skills.sh; 26.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need a team Drive for Project X but do not want to click through Admin console and sharing UI every time you spin up a collaboration space.
Who is it for?
Indie builders with Google Workspace and `gws-drive` who provision project drives and membership from an agent session.
Skip if: Personal My Drive folders only, or organizations where shared drive creation is locked to super admins without API access.
When should I use this skill?
You need to create a Google Shared Drive and add members with appropriate roles.
What do I get? / Deliverables
A named shared drive exists, at least one member has writer access, and permissions list confirms the roster.
- Created shared drive with chosen display name
- Member permission record (e.g. writer)
- Permissions list output for audit
Recommended Skills
Journey fit
Shared drives are structural workspace setup while you are building with collaborators—filesystem-like integration before day-to-day ops. Uses Drive `drives.create` and shared-drive-aware `permissions` with `supportsAllDrives`—integration with Google team storage APIs.
How it compares
Focused shared-drive bootstrap recipe—not a full Drive backup or sync integration.
Common Questions / FAQ
Who is recipe-create-shared-drive for?
Solo builders and tiny teams setting up Google Shared Drives for projects who prefer scripted create-and-member steps over console clicking.
When should I use recipe-create-shared-drive?
Use it during Build integrations when onboarding contractors or a micro-team folder, or in Operate infra when you standardize a new shared library for running work.
Is recipe-create-shared-drive safe to install?
It creates shared resources and grants write access; review the Security Audits panel on this page and double-check email addresses and roles before permissions create.
Workflow Chain
Requires first: gws drive
SKILL.md
READMESKILL.md - Recipe Create Shared Drive
# 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}'`