メニュー
View, create, and manage Google Calendar events for Dylan, Julia, or other accounts. Use when asked about schedule, appointments, meetings, calendar, what's coming up, free time, conflicts, or availability.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | gws-calendar |
| description | View, create, and manage Google Calendar events for Dylan, Julia, or other accounts. Use when asked about schedule, appointments, meetings, calendar, what's coming up, free time, conflicts, or availability. |
| allowed-tools | Bash(calendar:*) |
| metadata | {"openclaw":{"emoji":"📅","requires":{"bins":["gws"]}}} |
Access Google Calendar via the gws CLI at /opt/homebrew/bin/gws. Credentials are AES-256-GCM encrypted at ~/.config/gws/.
Read references/gws-cli.md before selecting an account, changing authentication, or executing a write.
| Account | Owner | Service-command selection |
|---|---|---|
| ${DYLAN_EMAIL} | Dylan | GOOGLE_WORKSPACE_CLI_ACCOUNT=${DYLAN_EMAIL} |
| ${JULIA_EMAIL} | Julia | GOOGLE_WORKSPACE_CLI_ACCOUNT=${JULIA_EMAIL} |
| ${STARMARKET_GMAIL} | Dylan (spam) | GOOGLE_WORKSPACE_CLI_ACCOUNT=${STARMARKET_GMAIL} |
| ${OPENCLAW_EMAIL} | OpenClaw | GOOGLE_WORKSPACE_CLI_ACCOUNT=${OPENCLAW_EMAIL} |
When Dylan asks about "my calendar", use default. When he says "Julia's calendar", use her account.
All raw API commands follow: GOOGLE_WORKSPACE_CLI_ACCOUNT=<email> gws calendar <resource> <method> [--params '<JSON>'] [--json '<JSON>']
--params = URL/query parameters (calendarId, timeMin, maxResults, etc.)--json = request body (for create/update)gws calendar calendarList list
# Today's events
gws calendar events list --params '{
"calendarId": "primary",
"timeMin": "2026-03-05T00:00:00-05:00",
"timeMax": "2026-03-06T00:00:00-05:00",
"singleEvents": true,
"orderBy": "startTime"
}'
# Next 7 days
gws calendar events list --params '{
"calendarId": "primary",
"timeMin": "2026-03-05T00:00:00-05:00",
"timeMax": "2026-03-12T00:00:00-05:00",
"singleEvents": true,
"orderBy": "startTime"
}'
# Julia's events today
GOOGLE_WORKSPACE_CLI_ACCOUNT=${JULIA_EMAIL} gws calendar events list --params '{
"calendarId": "primary",
"timeMin": "2026-03-05T00:00:00-05:00",
"timeMax": "2026-03-06T00:00:00-05:00",
"singleEvents": true,
"orderBy": "startTime"
}'
# All calendars (use calendarList first, then query each)
gws calendar events list --params '{
"calendarId": "<calendarId>",
"timeMin": "...",
"timeMax": "...",
"singleEvents": true,
"orderBy": "startTime"
}'
Important: Always compute timeMin/timeMax as RFC3339 timestamps with timezone. Use America/New_York (-05:00 EST / -04:00 EDT).
gws calendar events get --params '{
"calendarId": "primary",
"eventId": "<eventId>"
}'
Use the q parameter:
gws calendar events list --params '{
"calendarId": "primary",
"q": "dinner",
"timeMin": "2026-03-01T00:00:00-05:00",
"timeMax": "2026-03-31T00:00:00-05:00",
"singleEvents": true,
"orderBy": "startTime"
}'
gws calendar events insert --params '{"calendarId": "primary"}' --json '{
"summary": "Team Standup",
"description": "Daily sync",
"location": "Zoom",
"start": {"dateTime": "2026-03-10T09:00:00-05:00", "timeZone": "America/New_York"},
"end": {"dateTime": "2026-03-10T09:30:00-05:00", "timeZone": "America/New_York"},
"attendees": [
{"email": "person@example.com"}
]
}'
gws calendar events insert --params '{"calendarId": "primary"}' --json '{
"summary": "Vacation",
"start": {"date": "2026-03-15"},
"end": {"date": "2026-03-16"}
}'
gws calendar events insert --params '{"calendarId": "primary"}' --json '{
"summary": "Weekly Standup",
"start": {"dateTime": "2026-03-10T09:00:00-05:00", "timeZone": "America/New_York"},
"end": {"dateTime": "2026-03-10T09:15:00-05:00", "timeZone": "America/New_York"},
"recurrence": ["RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR"]
}'
| Pattern | RRULE |
|---|---|
| Every Monday | RRULE:FREQ=WEEKLY;BYDAY=MO |
| Every weekday | RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR |
| Biweekly Tuesday | RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=TU |
| Daily | RRULE:FREQ=DAILY |
| 1st of every month | RRULE:FREQ=MONTHLY;BYMONTHDAY=1 |
| First Friday of every month | RRULE:FREQ=MONTHLY;BYDAY=1FR |
| Weekly until end of year | RRULE:FREQ=WEEKLY;BYDAY=WE;UNTIL=20261231T235959Z |
gws calendar events insert --params '{"calendarId": "primary", "conferenceDataVersion": 1}' --json '{
"summary": "1:1 with Alice",
"start": {"dateTime": "2026-03-10T14:00:00-05:00", "timeZone": "America/New_York"},
"end": {"dateTime": "2026-03-10T14:30:00-05:00", "timeZone": "America/New_York"},
"attendees": [{"email": "attendee@example.com"}],
"conferenceData": {
"createRequest": {"requestId": "meet-1", "conferenceSolutionKey": {"type": "hangoutsMeet"}}
}
}'
gws calendar events patch --params '{
"calendarId": "primary",
"eventId": "<eventId>"
}' --json '{
"summary": "New Title",
"start": {"dateTime": "2026-03-10T10:00:00-05:00", "timeZone": "America/New_York"},
"end": {"dateTime": "2026-03-10T10:30:00-05:00", "timeZone": "America/New_York"}
}'
Use patch (not update) to only change specified fields.
gws calendar events delete --params '{
"calendarId": "primary",
"eventId": "<eventId>"
}'
gws calendar freebusy query --json '{
"timeMin": "2026-03-10T00:00:00-05:00",
"timeMax": "2026-03-10T23:59:59-05:00",
"items": [
{"id": "${DYLAN_EMAIL}"},
{"id": "${JULIA_EMAIL}"}
]
}'
First get the event, then patch the attendee status:
# Get the event to find your attendee entry
gws calendar events get --params '{"calendarId": "primary", "eventId": "<eventId>"}'
# Accept/decline by updating the event
gws calendar events patch --params '{
"calendarId": "primary",
"eventId": "<eventId>"
}' --json '{
"attendees": [{"email": "${DYLAN_EMAIL}", "responseStatus": "accepted"}]
}'
For any command, check available parameters:
gws schema calendar.events.list
gws schema calendar.events.insert
primary = default calendar for the account2026-03-10T09:00:00-05:00)singleEvents: true + orderBy: startTime when listing to expand recurring eventsrecurrence array with RRULE_ suffix) for single-instance changesgws outputs JSON by default — pipe through jq or parse directlyRead upcoming OpenTable reservations or handle attended ad-hoc OpenTable availability and exact-approval booking. Use for OpenTable account reads, attended restaurant searches, or a user-confirmed one-off reservation; route canonical recurring date-night, double-date, and quarterly-group jobs to the restaurant-book skill instead.
Stage tightly scoped background reservation monitoring for OpenTable or Resy after explicit bounded preauthorization. Resy may auto-book after approval; OpenTable remains notification-only until this runtime adapter integrates the deployed live reservations reader. Not for one-shot search, attended booking, or cancellation.
Search Resy, inspect availability, and handle attended ad-hoc Resy booking. Route canonical recurring date-night, double-date, and quarterly-dinner jobs to restaurant-book, and use restaurant-snipe only for bounded cancellation monitoring. Never use this skill for unattended cancellation.
Safely plan or execute a canonical standing-authorized restaurant cron scope across both Resy and OpenTable. Use only for the tracked date-night, double-date, and quarterly-dinner jobs; use the provider skills for attended ad-hoc work and restaurant-snipe for bounded monitoring.
Safely use exact 1Password fields during attended interactive work and maintain the protected OpenClaw secrets cache. Use for passwords, API keys, credentials, payment data, cache refreshes, or diagnosing credential access. Never use `op` from a LaunchAgent or any child process it starts.
Diagnose and fix 1Password CLI hangs or repeated TCC prompts in macOS LaunchAgent and other unattended contexts by converting the complete process tree to a protected cache-only credential contract.