How to use the Reschedule Google Calendar Meeting agent skill

What the skill makes the agent do

An agent skill is a folder containing a SKILL.md file with instructions that an AI agent loads when a request matches the skill. This one covers a single task: moving a Google Calendar event to a new time and automatically notifying all attendees.

The skill works in three steps: it finds the meeting, reads its details, then changes the start and end times. Because it relies on the gws command-line tool to talk to Google Calendar, it acts on your actual account rather than only giving advice.

What you need before installing

The skill cannot run on its own. The SKILL.md file lists three requirements: the gws command-line tool (the bin named gws), the gws-calendar skill, and an authenticated Google account with Google Calendar access.

Credentials for gws are configured separately and are not described in the skill file, so you will need to set up gws authentication yourself before this skill can do anything.

• gws command-line tool (binary: gws)
• gws-calendar skill, which the recipe says must be loaded first
• A Google account with Calendar access, with credentials configured for gws

Install the skill

Download the ZIP for this skill from our page and unzip it. To make it available to all your projects, place the unzipped folder in ~/.claude/skills/. To limit it to one project, place it in that project's .claude/skills/ folder.

If you use the Claude apps instead, open Settings, go to Capabilities, and upload the skill under Skills.

• Personal install: ~/.claude/skills/
• Project install: .claude/skills/ inside your project folder
• Claude apps: Settings → Capabilities → Skills → upload

Trigger the skill with a natural request

You do not need a special command. Ask the agent in plain language to move a specific meeting, and include the new time with its time zone so the agent can set both start and end correctly. The skill's own steps will look up the event first, so give enough detail to identify it, such as its title or the day it falls on.

Before the agent sends the change, check the new time it proposes. The skill is designed to notify every attendee, so a wrong time will reach everyone.

• "Move my 2pm Product sync on Wednesday to 3pm New York time and let everyone know."
• "Reschedule the design review with Priya from Thursday to next Monday at 10am Eastern."

Understand the commands the skill runs

The skill's steps map to three gws calls. It first lists your agenda to find the event, then fetches the event details by its ID, then patches the event with new start and end times. The update uses sendUpdates set to all, which is what causes attendees to receive notices.

You can read these commands to see exactly what will run. Here is the update step as written in the skill:

• Find the event: gws calendar +agenda
• Get event details: gws calendar events get with calendarId primary and the event ID
• Update the time: gws calendar events patch with sendUpdates all and new start and end dateTime values

Safety notes: scripts and network access

The skill runs scripts and uses the network, because each step calls gws, which connects to Google Calendar using your credentials. Changes are made to your real calendar and attendees are emailed by Google.

Use it when you are comfortable with that. The skill is not a good fit for moving a meeting quietly. It also does not describe how to handle recurring events or invitations with many attendees, so a single slot change there could affect people unexpectedly. For those cases, make the change yourself or confirm each step closely.

• Runs scripts: yes. Uses network: yes.
• Attendees receive update notices by design.
• Recurring events and large invitations are not covered in the skill file.

Tips for reliable results

Give the agent the exact meeting title and date to avoid it picking the wrong event. Always state the time zone, because the update step sets start and end with an explicit timeZone value.

Test on a meeting you own with a colleague who knows about the test, and read the proposed command before approving it.

• Include the title, date and current time of the meeting.
• State both the new start time and the time zone.
• Confirm the proposed command before it runs.