Recipe Schedule Recurring Event
- 24.3k installs
- 30k repo stars
- Updated July 22, 2026
- googleworkspace/cli
recipe-schedule-recurring-event is a Google Workspace CLI recipe that creates recurring calendar events with attendees.
About
recipe-schedule-recurring-event is a Google Workspace CLI recipe that creates recurring Google Calendar events with attendees using command-line automation. Software engineers use it to schedule team meetings programmatically. It combines the gws calendar skill with recurrence rules for repeating events.
- CLI-based Google Calendar event creation with recurrence rules
- Integrates Workspace APIs without boilerplate
- Structured JSON output for agent automation
Recipe Schedule Recurring Event by the numbers
- 24,323 all-time installs (skills.sh)
- +806 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #40 of 690 Office & Documents skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
recipe-schedule-recurring-event capabilities & compatibility
- Works with
- gmail · google drive
- Use cases
- orchestration · project management · planning
What recipe-schedule-recurring-event says it does
Create a recurring Google Calendar event with attendees.
npx skills add https://github.com/googleworkspace/cli --skill recipe-schedule-recurring-eventAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 24.3k |
|---|---|
| repo stars | ★ 30k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 22, 2026 |
| Repository | googleworkspace/cli ↗ |
How do you create recurring Google Calendar events from CLI?
Automate team meeting scheduling and calendar management via CLI
Who is it for?
Automating team meeting scheduling
Skip if: Teams using Outlook, Cal.com, or non-Google calendars who cannot provision events through gws calendar commands.
When should I use this skill?
You need to create recurring calendar events programmatically
What you get
A recurring Google Calendar event with defined time zone, recurrence rule, and attendee invitations.
- recurring google calendar event
- attendee invitations
By the numbers
- Metadata version 0.22.5
- Documents 1 primary gws calendar events insert step
Files
Schedule a Recurring Meeting
PREREQUISITE: Load the following skills to execute this recipe: gws-calendarCreate a recurring Google Calendar event with attendees.
Steps
1. Create recurring event: gws calendar events insert --params '{"calendarId": "primary"}' --json '{"summary": "Weekly Standup", "start": {"dateTime": "2024-03-18T09:00:00", "timeZone": "America/New_York"}, "end": {"dateTime": "2024-03-18T09:30:00", "timeZone": "America/New_York"}, "recurrence": ["RRULE:FREQ=WEEKLY;BYDAY=MO"], "attendees": [{"email": "team@company.com"}]}' 2. Verify it was created: gws calendar +agenda --days 14 --format table
Related skills
Lark DocGenerate, update, and maintain structured documentation directly inside Lark/Feishu using natural language and agentic workflows.475kLark DriveLet their coding agents read, create, update and search documents stored in Lark (Feishu) Drive directly from prompts.475kLark SheetsConnect Claude, Cursor or other agents directly to Feishu/Lark spreadsheets for live data reads, writes, and structured automation.474kLark WikiGenerate, update, and sync structured knowledge bases inside Lark (Feishu) directly from code, specs, or agent output.474kLark WhiteboardGenerate, edit, and collaborate on visual diagrams and flowcharts directly inside Claude, Cursor or other agents.474kLark SlidesInstantly generate polished, professional slide decks from specs, roadmaps, or meeting notes using Lark/Feishu.474kFAQ
What does this recipe do?
Creates recurring Google Calendar events with attendees using the gws CLI, supporting recurrence rules like WEEKLY on specific days
What prerequisites are needed?
The gws-calendar skill must be loaded, and you need the gws CLI installed
Is Recipe Schedule Recurring Event safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.