recipe-schedule-recurring-event
Create a recurring Google Calendar event with attendees.
Profile →npx skills add googleworkspace/cli --skill recipe-schedule-recurring-event --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Schedule a Recurring Meeting > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-calendar` Create a recurring Google Calendar event with attendees. ## Steps 1. Create recurring event: `gws calendar events insert --params '{"calendarId": "primary"}' --json '{"summary": "Weekly Standup", "start": {"dateTime": "2024-03-18T09:00:00", "timeZone": "America/New_York"}, "end": {"dateTime": "2024-03-18T09:30:00", "timeZone": "America/New_York"}, "recurrence": ["RRULE:FREQ=WEEKLY;BYDAY=MO"], "attendees": [{"email": "team@company.com"}]}'` 2. Verify it was created: `gws calendar +agenda --days 14 --format table`
- Steps
What does the recipe-schedule-recurring-event skill do?
Create a recurring Google Calendar event with attendees.
How do I install it?
Run `npx skills add googleworkspace/cli --skill recipe-schedule-recurring-event --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From googleworkspace/cli, a repository with 30,193 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.