Skip to content
Back to skills

Recipe Reschedule Meeting

ASecurity

Move a Google Calendar event to a new time and automatically notify all attendees.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 28, 2026
ai-agentsgobash

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add fakoli/fakoli-plugins --skill recipe-reschedule-meeting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Recipe Reschedule Meeting?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Recipe Reschedule Meeting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fakoli-recipe-reschedule-meeting/badge)](https://www.skillsdirectory.com/skills/fakoli-recipe-reschedule-meeting)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: recipe-reschedule-meeting
description: "Move a Google Calendar event to a new time and automatically notify all attendees."
trigger:
  - keyword: reschedule meeting
  - keyword: move meeting
  - keyword: change meeting time
version: 1.0.0
---

# Reschedule a Google Calendar Meeting

Move a Google Calendar event to a new time and automatically notify all attendees.

## When to Use

Use this workflow when the user needs to change the time of an existing meeting and wants attendees notified of the change.

## Workflow

### 1. Find the event

```bash
gws calendar +agenda --format table
```

Ask the user which event to reschedule.

### 2. Get event details

```bash
gws calendar events get \
  --params '{"calendarId": "primary", "eventId": "EVENT_ID"}' \
  --fields "summary,start,end,attendees"
```

### 3. Confirm the new time

Ask the user for the new date/time. Preview the change:

```bash
gws calendar events patch \
  --params '{"calendarId": "primary", "eventId": "EVENT_ID", "sendUpdates": "all"}' \
  --json '{"start": {"dateTime": "NEW_START", "timeZone": "TIMEZONE"}, "end": {"dateTime": "NEW_END", "timeZone": "TIMEZONE"}}' \
  --dry-run
```

### 4. Execute

After user confirmation, run without `--dry-run`. The `"sendUpdates": "all"` parameter ensures all attendees get notified.

## Safety

- Always `--dry-run` first
- `"sendUpdates": "all"` sends email notifications to all attendees — confirm this is desired

## Tips

- Preserve the event duration unless the user explicitly wants to change it
- Check for conflicts at the new time before rescheduling

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.