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:
Install
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://github.com/googleworkspace/cli/blob/main/skills/recipe-share-event-materials/SKILL.md 1. Fetch the SKILL.md file for the googleworkspace-cli-recipe-share-event-materials skill from the repository into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.