Recipe Share Event Materials
Grant Google Drive read access to every attendee on a calendar event without hand-typing each share dialog.
Overview
Recipe Share Event Materials is an agent skill for the Build phase that shares a Google Drive file with all attendees of a Google Calendar event via gws CLI commands.
Install
npx skills add https://github.com/googleworkspace/cli --skill recipe-share-event-materialsWhat is this skill?
- 3-step recipe: list event attendees, create reader permissions per email, verify with permissions table
- Requires loaded gws-calendar and gws-drive skills plus the gws binary
- Uses gws calendar events get and drive permissions create/list with JSON params
- OpenClaw recipe metadata: domain productivity, category recipe
- prerequisite skills: gws-calendar and gws-drive
Adoption & trust: 15.1k installs on skills.sh; 26.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have meeting materials on Drive but sharing them one-by-one to every calendar invitee is slow and error-prone.
Who is it for?
Operators or builders who already run gws with calendar and drive skills loaded and need a post-meeting share ritual.
Skip if: Teams without gws auth, bulk public links, or org-wide Drive policies that forbid per-user reader grants.
When should I use this skill?
Share Google Drive files with all attendees of a Google Calendar event.
What do I get? / Deliverables
Each event attendee receives reader access on the target file, with permissions verifiable in a table listing after the recipe runs.
- Drive reader permissions for each attendee
- Verified permissions table output
Recommended Skills
Journey fit
Recipes sit on the build shelf because they wire Google Calendar and Drive together through the gws CLI—classic integration work during product or ops setup. integrations is the canonical subphase for third-party API/CLI glue (Workspace, not app UI).
How it compares
Use this procedural recipe instead of ad-hoc UI sharing when you want agent-repeatable Workspace automation.
Common Questions / FAQ
Who is recipe-share-event-materials for?
Solo builders and indie teams using the Google Workspace CLI who want agents to share Drive files with calendar attendees after events.
When should I use recipe-share-event-materials?
Use it in Build (integrations) after a meeting when you have an event ID and file ID and need reader permissions for every attendee; also handy in Operate when standardizing post-call material distribution.
Is recipe-share-event-materials safe to install?
It only documents gws commands that modify Drive ACLs for real attendee emails—review the Security Audits panel on this page and confirm sharing scope before running in production calendars.
Workflow Chain
Requires first: gws calendar, gws drive
SKILL.md
READMESKILL.md - Recipe Share Event Materials
# Share Files with Meeting Attendees > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-calendar`, `gws-drive` Share Google Drive files with all attendees of a Google Calendar event. ## Steps 1. Get event attendees: `gws calendar events get --params '{"calendarId": "primary", "eventId": "EVENT_ID"}'` 2. Share file with each attendee: `gws drive permissions create --params '{"fileId": "FILE_ID"}' --json '{"role": "reader", "type": "user", "emailAddress": "attendee@company.com"}'` 3. Verify sharing: `gws drive permissions list --params '{"fileId": "FILE_ID"}' --format table`