Guide · Agent skill
How to use the Batch Invite Attendees to Calendar Event agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
This guide explains the Batch Invite Attendees to Calendar Event agent skill (skill name recipe-batch-invite-to-event), which lets an AI agent add a list of people to a Google Calendar event you already have and have Google notify them. It is for organizers and assistants who manage meetings for a team. By the end you will know how to install the skill, how to ask for it in plain language, and what it needs before it can work.
Batch Invite Attendees to Calendar Eventgoogleworkspace/cli · Apache-2.0 Download the skill Quick start
- 1Download the ZIP. Download the skill ZIP from this page.
- 2Install the skill. Unzip into ~/.claude/skills/ or a project's .claude/skills/, or upload the ZIP under Settings → Capabilities → Skills in the Claude apps.
- 3Install gws and load gws-calendar. Make sure the gws command-line tool is available and the gws-calendar skill is loaded.
- 4Authorize Google Calendar access. Confirm your Google account is authorized for Google Calendar access through gws.
- 5Ask for the change. Name the existing event and list the email addresses to add in plain language.
- 6Check the result. Review the attendee list the agent confirms after the patch.
What the skill makes the agent do
Agent skills are instruction packages that give an AI agent a specific, repeatable procedure. This skill covers one task: adding a list of email addresses as attendees to an event that already exists in Google Calendar, and having Google send those people update notifications.
The skill follows three steps. First it fetches the event. Then it patches the event with the new attendees and notifications enabled. Finally it fetches the event again to confirm the attendee list.
- It only modifies an existing event, identified by its event ID.
- It does not create new events.
- It relies on the gws command-line tool and the gws-calendar skill to talk to Google Calendar.
Install the skill from the ZIP download
Download the ZIP for this skill from this page, then choose one of two ways to install it.
For Claude Code, unzip the file into your personal skills folder ~/.claude/skills/ or into a project's .claude/skills/ folder if you want the skill limited to one project. The skill's SKILL.md file should sit inside the skill folder after unzipping.
For the Claude apps, open Settings, go to Capabilities, then Skills, and upload the ZIP there.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside your project
- Claude apps: Settings → Capabilities → Skills
Set up the prerequisites
The skill will not run on its own. It needs the gws command-line tool installed and available as gws, the gws-calendar skill loaded, and a Google account that is authorized for Google Calendar access through gws.
The SKILL.md file lists gws-calendar as a required skill. Load it alongside this one before running the recipe.
- gws command-line tool (binary name: gws)
- gws-calendar skill
- Google account authorized for Google Calendar access via gws
Ask the agent for it with natural requests
You do not need to type commands yourself. Describe the event and the people you want to add, and name the event clearly enough for the agent to find its event ID. The skill is designed to add several attendees in one change.
Good requests state the event, the people and whether they should be notified. For example: add alice@company.com, bob@company.com and carol@company.com to Thursday's design review on my primary calendar and send them invitations.
- "Add alice@company.com, bob@company.com and carol@company.com to the Q3 planning event on my primary calendar and notify them."
- "Invite these three colleagues to the event with ID abc123 and confirm the attendee list afterwards."
Understand what the commands do
The source uses the primary calendar and an EVENT_ID placeholder. The first command gets the event, the second patches the attendee list with sendUpdates set to all, and the third gets the event again to verify the result.
Because sendUpdates is set to all, Google emails every person on the list. Use this skill only when that is what you want.
gws calendar events get --params '{"calendarId": "primary", "eventId": "EVENT_ID"}'
gws calendar events patch --params '{"calendarId": "primary", "eventId": "EVENT_ID", "sendUpdates": "all"}' --json '{"attendees": [{"email": "alice@company.com"}, {"email": "bob@company.com"}, {"email": "carol@company.com"}]}'
gws calendar events get --params '{"calendarId": "primary", "eventId": "EVENT_ID"}'Safety notes: scripts and network access
This skill runs scripts and uses the network. Its commands send requests to Google Calendar using your authorized account, so the agent can read and change events on that calendar.
Check the event ID and the attendee list before the agent runs the patch. Changes affect the real event, and notifications go out to every address you include. The skill also requires edit rights on the calendar; without them the change will fail or may affect the wrong event.
- Confirm the event ID matches the meeting you intend to change.
- Double-check every email address before sending.
- Use only calendars you have edit rights to.
Tips for reliable results
Give the agent the event ID when you have it. The skill works from an event ID, so a precise reference avoids guessing.
Review the verification step. The third command fetches the event again so you can see the final attendee list.
If you do not want invitees notified, do not use this skill, because it sets sendUpdates to all.
- Provide the event ID or a precise event name.
- Check the final attendee list the agent reports back.
- Pick a different approach when silent updates are required.
What people use it for
- Adding a group of colleagues to a meeting after it was created.
- An assistant inviting several team members to an event on a manager's calendar.
- Extending a planning session to additional attendees without recreating the event.
- Confirming the final attendee list for a meeting by fetching the event again.
Frequently asked questions
How do I install the batch invite attendees agent skill?
Download the ZIP from this page. In Claude Code, unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. In the Claude apps, upload it under Settings → Capabilities → Skills.
What does the recipe-batch-invite-to-event skill require?
It requires the gws command-line tool (binary gws), the gws-calendar skill, and a Google account authorized for Google Calendar access through gws. It runs scripts and uses the network.
Is this skill free?
The source material for this skill is licensed under Apache-2.0. It does not state pricing, so check the licence terms for the gws tool and your own Google account requirements.
Can this skill create a new calendar event?
No. The skill only adds attendees to an existing event identified by its event ID. It is not designed to create new events.
Can I add attendees without sending email notifications?
Not with this skill. It sets sendUpdates to all, so Google notifies everyone on the list. If invitees should not be notified automatically, choose a different approach.
What should I do if the attendee change fails?
Check that you have edit rights to the calendar, that the event ID is correct, and that gws is authorized for your Google account. Without edit rights the change will fail or may affect the wrong event.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits organizers and calendar assistants who need to add several people to an event that already exists and want Google to notify them. It is a poor fit if you need to create new events, or if invitees must not receive automatic emails, or if you lack edit rights to the calendar.
Download the skill