How to use the Schedule Recurring Meeting agent skill

What is an agent skill and what does this one do?

An agent skill is a folder containing a SKILL.md file with instructions that an AI agent can load and follow. This skill is a recipe: it tells the agent how to create a recurring Google Calendar event with attendees, then how to check the result.

The recipe has two steps. First, it creates the recurring event with the gws calendar events insert command. Second, it runs gws calendar +agenda with a 14-day window to confirm the event now appears in the agenda.

• Creates a recurring Google Calendar event with a summary, start and end time, time zone and recurrence rule.
• Adds attendees by email address.
• Checks the agenda for the next two weeks to confirm the event exists.

What you need before installing

The skill cannot run on its own. It depends on the gws command-line tool and on the gws-calendar skill, which must be loaded first. The source does not state the exact authorisation setup, so you need a Google account that is authorised for Google Calendar through gws, following the gws tool's own setup.

• The gws command-line tool (the skill requires the gws binary).
• The gws-calendar skill, loaded before this recipe runs.
• A Google account authorised for Google Calendar through gws.

How do you install the skill?

Download the ZIP file from this page and unzip it. The skill is a single file, SKILL.md, inside the folder.

For a personal install, unzip it into ~/.claude/skills/. For a single project, unzip it into the project's .claude/skills/ folder.

If you use the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.

• Personal: ~/.claude/skills/
• Project only: .claude/skills/ inside your project folder
• Claude apps: Settings → Capabilities → Skills, then upload the ZIP

How do you trigger the skill with a natural request?

You do not need to type the calendar commands yourself. Describe the meeting in plain language, including the title, the schedule, the time zone and who should attend. The agent should then follow the recipe.

Be specific. Give a start date and time, a time zone, how often the meeting repeats and the attendee addresses. Vague requests make it more likely the agent will guess the details.

• "Set up a weekly standup called Weekly Standup every Monday at 9:00 am New York time, starting March 18, 2024, and invite team@company.com."
• "Create a recurring 30-minute team sync on Tuesdays at 2 pm Eastern with alice@company.com and bob@company.com."
• "Schedule a weekly Monday meeting for my group and then show me the next two weeks of my calendar."

What the recipe runs behind the scenes

The recipe uses the following commands. The event in the example is a Weekly Standup on Mondays, starting 18 March 2024 at 09:00 in America/New_York, lasting 30 minutes, with a placeholder attendee address. Treat these values as an example, not as defaults for your calendar.

The second command lists the agenda for 14 days in table format, which is how the agent checks that the event was created.

Safety notes: scripts and network access

This skill runs scripts and uses the network. The recipe sends attendee invitations directly, so the calendar change is real as soon as the agent runs it. The example hard-codes a calendar ID of primary, fixed times and a placeholder address, so an agent that reuses these values without checking could create an event with the wrong details or invite the wrong people.

Before you rely on the skill for real invitations, ask the agent to show you the exact command and details first, and confirm the attendee list and time zone.

• Check the title, date, time, time zone, recurrence rule and every attendee before confirming.
• Test with an address you control before inviting a real group.
• Remember that invitations are sent directly, not drafted for review.

Tips for getting reliable results

Keep the time zone explicit in every request, because the example stores start and end times with a named zone. Use a single weekday in the recurrence where possible, since the example uses BYDAY=MO for Mondays.

If the event does not show up, check the agenda yourself and make sure gws is authorised for the calendar you expect.

• Always name the time zone.
• Name the weekday and frequency clearly.
• Ask for the two-week agenda check so you can see the result.