Recipe Share Doc And Notify
Automate finding a Google Doc, granting editor access, and emailing collaborators the link via the gws CLI recipe.
Overview
Recipe Share Doc And Notify is an agent skill for the Build phase that shares a Google Doc with edit access and emails collaborators the link using gws CLI steps.
Install
npx skills add https://github.com/googleworkspace/cli --skill recipe-share-doc-and-notifyWhat is this skill?
- OpenClaw recipe metadata v0.22.5 requiring gws binary plus gws-drive, gws-docs, gws-gmail skills
- Step 1: Drive search by name and Google Docs mimeType for Project Brief
- Step 2: permissions create with writer role for a specific email
- Step 3: gmail +send with subject, body, and docs.google.com link
- Explicit prerequisite load of three sibling skills before execution
- Recipe metadata version 0.22.5
- 3 sequential steps: list doc, create permission, send email
- Requires 3 prerequisite gws skills plus gws CLI binary
Adoption & trust: 15.5k installs on skills.sh; 26.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a Google Doc brief but manually sharing editor access and emailing the link breaks your agent automation flow.
Who is it for?
Builders already using gws CLI who want a fixed recipe for doc sharing plus notify on projects like 'Project Brief'.
Skip if: Teams without Google Workspace, without gws installed, or when you only need in-doc comments without email notification.
When should I use this skill?
Share a Google Docs document with edit access and email collaborators the link using gws.
What do I get? / Deliverables
Collaborators receive writer permissions and a Gmail with the document link after a scripted Drive search and permission create sequence.
- Drive permission with writer role for specified email
- Sent Gmail message containing the Google Doc URL
Recommended Skills
Journey fit
This recipe wires Google Drive, Docs, and Gmail together—classic build-phase integration work for solo builders automating handoffs. Integrations subphase fits multi-API CLI choreography rather than writing frontend UI or launch SEO.
How it compares
Recipe-style skill package for gws command chains, not a hosted MCP server or Google Apps Script UI wizard.
Common Questions / FAQ
Who is recipe share doc and notify for?
Solo and indie builders automating Google Workspace handoffs with the gws CLI and OpenClaw-style agent recipes.
When should I use recipe share doc and notify?
During build integrations when a spec or brief doc must be shared with editor access and the collaborator must be emailed the link in one flow.
Is recipe share doc and notify safe to install?
It uses Drive permissions and Gmail send capabilities; review the Security Audits panel on this Prism page and scope OAuth tokens before running on production Workspace accounts.
SKILL.md
READMESKILL.md - Recipe Share Doc And Notify
# Share a Google Doc and Notify Collaborators > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-drive`, `gws-docs`, `gws-gmail` Share a Google Docs document with edit access and email collaborators the link. ## Steps 1. Find the doc: `gws drive files list --params '{"q": "name contains '\''Project Brief'\'' and mimeType = '\''application/vnd.google-apps.document'\''"}'` 2. Share with editor access: `gws drive permissions create --params '{"fileId": "DOC_ID"}' --json '{"role": "writer", "type": "user", "emailAddress": "reviewer@company.com"}'` 3. Email the link: `gws gmail +send --to reviewer@company.com --subject 'Please review: Project Brief' --body 'I have shared the project brief with you: https://docs.google.com/document/d/DOC_ID'`