Skip to content
Back to skills

Recipe Schedule Recurring Event

ASecurity

Create a recurring Google Calendar event with 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-schedule-recurring-event --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Recipe Schedule Recurring Event?

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

Security grade badge for Recipe Schedule Recurring Event
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fakoli-recipe-schedule-recurring-event/badge)](https://www.skillsdirectory.com/skills/fakoli-recipe-schedule-recurring-event)

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-schedule-recurring-event
description: "Create a recurring Google Calendar event with attendees."
trigger:
  - keyword: recurring event
  - keyword: recurring meeting
  - keyword: weekly meeting
version: 1.0.0
---

# Schedule a Recurring Meeting

Create a recurring Google Calendar event with attendees.

## When to Use

Use this workflow when the user wants to set up a repeating meeting — weekly standups, biweekly 1:1s, monthly reviews, etc.

## Workflow

### 1. Gather details

Ask the user for:
- **Title** (e.g., "Weekly Standup")
- **Day/time** and timezone
- **Duration**
- **Recurrence pattern** (weekly, biweekly, monthly)
- **Attendees** (email addresses)

### 2. Build the recurrence rule

Common RRULE patterns:
- Weekly on Monday: `RRULE:FREQ=WEEKLY;BYDAY=MO`
- Biweekly on Tuesday: `RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=TU`
- Monthly first Wednesday: `RRULE:FREQ=MONTHLY;BYDAY=1WE`
- Daily weekdays: `RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR`

### 3. Create the event

```bash
gws calendar events insert \
  --params '{"calendarId": "primary"}' \
  --json '{"summary": "TITLE", "start": {"dateTime": "START", "timeZone": "TZ"}, "end": {"dateTime": "END", "timeZone": "TZ"}, "recurrence": ["RRULE"], "attendees": [{"email": "ATTENDEE"}]}' \
  --dry-run
```

Confirm with the user, then execute.

### 4. Verify

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

## Safety

- Always `--dry-run` first — recurring events create many instances
- Add `COUNT=N` to the RRULE to limit the number of occurrences

## Tips

- Use `UNTIL=20261231T000000Z` in the RRULE to set an end date
- The first occurrence date is set by the `start` field, not the RRULE

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.