recipe-reschedule-meeting
Move a Google Calendar event to a new time and automatically notify all attendees.
Profile →npx skills add googleworkspace/cli --skill recipe-reschedule-meeting --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.
# Reschedule a Google Calendar Meeting > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-calendar` Move a Google Calendar event to a new time and automatically notify all attendees. ## Steps 1. Find the event: `gws calendar +agenda` 2. Get event details: `gws calendar events get --params '{"calendarId": "primary", "eventId": "EVENT_ID"}'` 3. Update the time: `gws calendar events patch --params '{"calendarId": "primary", "eventId": "EVENT_ID", "sendUpdates": "all"}' --json '{"start": {"dateTime": "2025-01-22T14:00:00", "timeZone": "America/New_York"}, "end": {"dateTime": "2025-01-22T15:00:00", "timeZone": "America/New_York"}}'`
- Steps
What does the recipe-reschedule-meeting skill do?
Move a Google Calendar event to a new time and automatically notify all attendees.
How do I install it?
Run `npx skills add googleworkspace/cli --skill recipe-reschedule-meeting --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.