google-calendar

Interact with Google Calendar - list calendars, view events, create/update/delete events, and find free time. Use when user asks to: check calendar, schedule a meeting, create an event, find available time, list upcoming events, delete or update a calendar event, or respond to meeting invitations. Lightweight alternative to full Google Workspace MCP server with standalone OAuth authentication.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable command catalog with executable examples for every operation, weakened mainly by absent validation/verification steps around destructive and batch calendar operations.

Suggestions

Add a verification step after create/update/delete — e.g. 'After creating, run gcal.py get-event <id> to confirm the event details landed correctly' — to satisfy the destructive-operations workflow checkpoint.

For find-free-time across multiple attendees, note how to validate the returned slot (confirm attendee availability / send invites) before booking, since this is a batch operation.

Trim the standalone 'Token Management' section or fold it into First-Time Setup, as it repeats the auth.py workflow already covered above.

Dimension	Reasoning	Score
Conciseness	Mostly lean command reference that assumes competence; minor padding like the 'All operations via scripts/gcal.py' lead-in and the standalone-token-management section could be trimmed, but nothing qualifies as concept over-explanation.	4 / 5
Actionability	Every command is a fully executable, copy-paste-ready invocation with concrete arguments (EVENT_ID, ISO timestamps, attendee emails), and the common cases for each operation are illustrated with real flag combinations.	5 / 5
Workflow Clarity	Commands are well grouped, but destructive/batch operations (create/update/delete, find-free-time over multiple attendees) have no explicit validation or verification step — e.g. no 'verify the event was created with get-event' after create, which caps the score at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Good single-file structure with clear section headers for setup, commands, formats, and token management; bundle scripts (scripts/auth.py, scripts/gcal.py, scripts/requirements.txt) are referenced one level deep and exist, though there are no separate reference docs for deeper detail.	4 / 5
	Total	16 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-crafted description that names concrete capabilities and pairs them with explicit, naturally phrased 'Use when' triggers, while staking out a distinct niche relative to the full MCP server.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'list calendars, view events, create/update/delete events, and find free time' — covering the full CRUD surface of Google Calendar with comprehensive, specific coverage.	5 / 5
Completeness	Explicitly answers both 'what' (the CRUD + free-time capability list) and 'when' via a concrete 'Use when user asks to:' clause enumerating specific trigger phrases.	5 / 5
Trigger Term Quality	Strong natural triggers ('check calendar', 'schedule a meeting', 'create an event', 'find available time', 'list upcoming events'); a few common variants (e.g. 'reschedule', 'book', 'what's on my calendar') are missing.	4 / 5
Distinctiveness Conflict Risk	The 'Lightweight alternative to full Google Workspace MCP server with standalone OAuth' framing carves out a clear niche, but the calendar trigger set still has minor overlap risk with broader scheduling/workspace skills.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: sanjay3290/ai-skills
Path: skills/google-calendar/SKILL.md
Commit: 281d88d

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.