gws recipe: Share event materials
Cross-service Calendar-to-Drive flow — share files with every attendee of an event
- What
- Cross-service Calendar-to-Drive flow — share files with every attendee of an event
- Cost
- Free
- Needs
- the `gws` binary on the PATH (see the repo README for install options); a Google account (browser OAuth via `gws auth login`, interactive and free); the `gws-shared` and `gws-calendar` prerequisite skills installed first (`gws-drive` is used too — same repo, not listed in this catalog)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
💳 Curated by Skill Harbor — the share-event-materials recipe: the cross-service flow « share the meeting docs with everyone » — get the event's attendees via the Calendar API, then grant each attendee file permissions on Drive, in 3 steps. Distinct from `googleworkspace-cli-recipe-batch-invite-to-event` in this lot (which manages attendees, not files): this one manages files for existing attendees. By @googleworkspace, listed here with credit to its creator. Honest caveats: requires the `gws` binary and a Google account (browser OAuth is free); the `gws-drive` prerequisite comes from the same repo but is not listed in this catalog; install the prerequisite `googleworkspace-cli-gws-shared` first. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
gws recipe Share event materials is a free Muse skill for the flow of sharing meeting docs with everyone: get the event's attendees via the Calendar API, then grant each attendee permissions on Drive. Distinct from the batch-invite recipe, which manages attendees, not files, this one manages files for attendees, and requires the gws binary and a Google account.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit a3768d0Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: the `gws` binary on the PATH (see the repo README for install options); a Google account (browser OAuth via `gws auth login`, interactive and free); the `gws-shared` and `gws-calendar` prerequisite skills installed first (`gws-drive` is used too — same repo, not listed in this catalog) Install "gws recipe: Share event materials" for me. Teach my agent the cross-service flow — get an event's attendees via the Calendar API, then share a Drive file with every attendee in 3 steps Repository: https://raw.githubusercontent.com/googleworkspace/cli/a3768d0e82ad83cca2da97724e46bea4ff0e6dbd/skills/recipe-share-event-materials/SKILL.md Pinned version: install the code at commit a3768d0e82ad83cca2da97724e46bea4ff0e6dbd exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the googleworkspace-cli-recipe-share-event-materials skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "googleworkspace-cli-recipe-share-event-materials". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the gws binary, run `gws auth login`). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- a3768d0 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.