← Search

gws recipe: Schedule a recurring meeting
Productivity 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit a3768d0
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: the `gws` binary on the PATH (see the repo README…

gws recipe: Schedule a recurring meeting

Recurring team meeting with attendees in two commands — verified with the agenda

At a glance
What
Recurring team meeting with attendees in two commands — verified with the agenda
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
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@

Quick answer

Schedule a recurring meeting is a free Muse skill, the schedule-recurring-event recipe for creating a recurring team meeting with attendees in two commands. It inserts the event with a weekly RRULE and attendees, then verifies with the agenda command over fourteen days. It is distinct from solo focus blocks, which have no attendees.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit a3768d0

Step 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 Install "gws recipe: Schedule a recurring meeting" for me. Teach my agent to create a recurring team meeting with attendees in two commands — events insert with a weekly RRULE and attendees, then verify with +agenda Repository: https://raw.githubusercontent.com/googleworkspace/cli/a3768d0e82ad83cca2da97724e46bea4ff0e6dbd/skills/recipe-schedule-recurring-event/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-schedule-recurring-event 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-schedule-recurring-event". 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit a3768d0 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : registry.npmjs.org
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
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
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

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.