Create, update, and manage Google Calendar events with availability checking and scheduling.
Works with
Supports core event operations: create, update, delete, and list events across specified time ranges with automatic pagination
Includes free/busy availability checking across multiple calendars to find open time slots for scheduling
OAuth 2.0 authentication with keyring-based credential storage; declined invitations are filtered by default but can be included on demand
Commands use RFC3339
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongoogle-calendarExecute the skills CLI command in your project's root directory to begin installation:
Fetches google-calendar from odyssey4me/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate google-calendar. Access via /google-calendar in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
2
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
2
stars
Interact with Google Calendar for event management, scheduling, and availability checking.
Dependencies: pip install --user google-auth google-auth-oauthlib google-api-python-client keyring pyyaml
After installation, verify the skill is properly configured:
$SKILL_DIR/scripts/google-calendar.py check
This will check:
If anything is missing, the check command will provide setup instructions.
Google Calendar uses OAuth 2.0 for authentication. For complete setup instructions, see:
Create ~/.config/agent-skills/google.yaml:
oauth_client:
client_id: your-client-id.apps.googleusercontent.com
client_secret: your-client-secret
Run $SKILL_DIR/scripts/google-calendar.py check to trigger OAuth flow and verify setup.
On scope or authentication errors, see the OAuth troubleshooting guide.
See permissions.md for read/write classification of each command.
# Setup and auth
$SKILL_DIR/scripts/google-calendar.py check
$SKILL_DIR/scripts/google-calendar.py auth setup --client-id ID --client-secret SECRET
$SKILL_DIR/scripts/google-calendar.py auth reset
$SKILL_DIR/scripts/google-calendar.py auth status
# Calendars
$SKILL_DIR/scripts/google-calendar.py calendars list
$SKILL_DIR/scripts/google-calendar.py calendars get CALENDAR_ID
# Events
$SKILL_DIR/scripts/google-calendar.py events list
$SKILL_DIR/scripts/google-calendar.py events get EVENT_ID
$SKILL_DIR/scripts/google-calendar.py events create --summary TITLE --start TIME --end TIME
$SKILL_DIR/scripts/google-calendar.py events update EVENT_ID --summary TITLE
$SKILL_DIR/scripts/google-calendar.py events delete EVENT_ID
# Availability
$SKILL_DIR/scripts/google-calendar.py freebusy --start TIME --end TIME
All commands support --calendar CALENDAR_ID (default: "primary"). Times use RFC3339 format (e.g., 2026-01-24T10:00:00Z) or YYYY-MM-DD for all-day events.
See command-reference.md for full argument details and examples.
$SKILL_DIR/scripts/google-calendar.py events create \
--summary "Team Standup" \
--start "2026-01-25T09:00:00-05:00" \
--end "2026-01-25T09:30:00-05:00" \
--location "Zoom" \
--attendees "[email protected]"
$SKILL_DIR/scripts/google-calendar.py freebusy \
--start "2026-01-24T08:00:00-05:00" \
--end "2026-01-24T17:00:00-05:00" \
--calendars "primary,[email protected]"
$SKILL_DIR/scripts/google-calendar.py events list \
--time-min "2026-01-24T00:00:00Z" \
--time-max "2026-01-31T23:59:59Z"
Event listing automatically paginates through all results. When a time range is specified, all matching events are returned regardless of count — results are never silently truncated.
When listing events, declined meetings are excluded by default. The script output will indicate if declined invitations were filtered out (e.g. "3 declined invitation(s) not shown"). When this notice appears, inform the user that there are declined invitations and offer to show them if desired. To include declined events, re-run with --include-declined.
Authentication and scope errors are not retryable. If a command fails with an authentication error, insufficient scope error, or permission denied error (exit code 1), stop and inform the user. Do not retry or attempt to fix the issue autonomously — these errors require user interaction (browser-based OAuth consent). Point the user to the OAuth troubleshooting guide.
Retryable errors: Rate limiting (HTTP 429) and temporary server errors (HTTP 5xx) may succeed on retry after a brief wait. All other errors should be reported to the user.
This skill makes API calls requiring structured input/output. A standard-capability model is recommended.
Verify the event ID and calendar ID are correct. Event IDs are unique per calendar.
Always use RFC3339 format with explicit timezone offsets, or UTC (Z suffix). For all-day events, use YYYY-MM-DD format and optionally specify --timezone.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
kostja94/marketing-skills
glebis/claude-skills
jwynia/agent-skills
mindrally/skills
github/awesome-copilot
wispbit-ai/skills
Keeps context tight: google-calendar is the kind of skill you can hand to a new teammate without a long onboarding doc.
google-calendar is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for google-calendar matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: google-calendar is focused, and the summary matches what you get after install.
google-calendar is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: google-calendar is the kind of skill you can hand to a new teammate without a long onboarding doc.
google-calendar reduced setup friction for our internal harness; good balance of opinion and flexibility.
google-calendar has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend google-calendar for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added google-calendar from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 30