Gcal
Apps & AutomationgcalGcal is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Google Calendar CLI for listing calendars, managing events, and checking availability. Use when you need to view, create, update, or delete calendar events, check free/busy status, or list calendars.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/gcal/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gcal, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Google Calendar CLI (gccli)
You have access to gccli - a minimal Google Calendar CLI. All commands use the format:
gccli <email> <command> [options]
Available Accounts
Commands
List Calendars
gccli <email> calendars
Returns: ID, name, access role.
List Events
gccli <email> events <calendarId> [options]
Options:
--from <datetime>- Start time (ISO 8601, default: now)--to <datetime>- End time (ISO 8601, default: 1 week from now)--max <n>- Max results (default: 10)--query <q>- Free text search
Examples:
gccli [email protected] events primary
gccli [email protected] events primary --from 2024-01-01T00:00:00Z --max 50
gccli [email protected] events primary --query "meeting"
Get Event Details
gccli <email> event <calendarId> <eventId>
Create Event
gccli <email> create <calendarId> --summary <s> --start <dt> --end <dt> [options]
Options:
--summary <s>- Event title (required)--start <datetime>- Start time (required, ISO 8601)--end <datetime>- End time (required, ISO 8601)--description <d>- Event description--location <l>- Event location--attendees <emails>- Attendees (comma-separated)--all-day- Create all-day event (use YYYY-MM-DD for start/end)
Examples:
gccli [email protected] create primary --summary "Meeting" --start 2024-01-15T10:00:00 --end 2024-01-15T11:00:00
gccli [email protected] create primary --summary "Vacation" --start 2024-01-20 --end 2024-01-25 --all-day
gccli [email protected] create primary --summary "Team Sync" --start 2024-01-15T14:00:00 --end 2024-01-15T15:00:00 --attendees [email protected],[email protected]
Update Event
gccli <email> update <calendarId> <eventId> [options]
Options: same as create (all optional).
Delete Event
gccli <email> delete <calendarId> <eventId>
Check Free/Busy
gccli <email> freebusy <calendarIds> --from <dt> --to <dt>
Calendar IDs are comma-separated.
Example:
gccli [email protected] freebusy primary,[email protected] --from 2024-01-15T00:00:00Z --to 2024-01-16T00:00:00Z
List Access Control Rules
gccli <email> acl <calendarId>
Returns: scope type, scope value, role.
Notes
- Use
primaryas calendarId to reference the main calendar - Date/times should be ISO 8601 format (e.g., 2024-01-15T10:00:00 or 2024-01-15T10:00:00Z)
- For all-day events, use date format YYYY-MM-DD