google-calendar-automation

Lightweight Google Calendar integration with standalone OAuth authentication. No MCP server required.

Quality

58%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/google-calendar-automation/SKILL.md

The canonical home for this skill is google-calendar in sanjay3290/ai-skills

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.

The body is a tight, highly actionable CLI reference with copy-paste commands across all calendar operations and good section organization. Its main gap is the absence of validation/confirmation steps for destructive (delete-event) and batch (find-free-time) operations, which caps workflow clarity.

Suggestions

Add a validation checkpoint before/after destructive ops, e.g. recommend running 'get-event EVENT_ID' to confirm before 'delete-event', and a post-delete verification step.

For find-free-time and batch attendee operations, note how to verify the returned slot is still free (e.g. re-check or create the event and confirm) to close the feedback loop.

Drop the duplicated opening line (it restates the frontmatter description verbatim) to tighten conciseness from 4 toward 5.

Dimension	Reasoning	Score
Conciseness	The body is lean command-reference prose with no padding about what Google Calendar or OAuth is; each code block earns its place, with only minor trimmable repetition (the opening line re-states the description), matching the score-4 anchor 'Efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	Every section gives copy-paste-ready executable commands (e.g. 'python scripts/gcal.py create-event "Team Meeting" ... --attendees user1@example.com') covering list, get, create, update, delete, find-free-time, and respond, matching the score-5 anchor 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	Setup is sequenced (login/status/logout) and commands are well-organized, but destructive and batch operations — 'delete-event EVENT_ID' and multi-attendee 'find-free-time' — have no validation/verification or feedback loop, so per the destructive/batch cap workflow_clarity cannot exceed the score-3 anchor 'Steps listed but validation gaps; checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	Content is a single well-organized file with clear section headers and no nested/deep references; the only referenced paths are the implementation scripts (scripts/auth.py, scripts/gcal.py), not documentation hops, matching the score-4 anchor 'Good structure; most content is appropriately placed; references mostly clear'.	4 / 5
	Total	16 / 20 Passed

Description

40%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.

The description names a clear, distinctive niche (Google Calendar with standalone OAuth, no MCP) but is thin on concrete capabilities and entirely lacks a 'Use when...' trigger clause. It reads as a tagline rather than a trigger-rich skill description.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks to manage Google Calendar events, schedule meetings, check availability, or respond to invitations.'

Replace the generic word 'integration' with 2-3 concrete actions such as 'list, create, update, and delete calendar events, find free time, and respond to invitations'.

Include common synonyms/file-type-style triggers ('events', 'appointments', 'scheduling', 'free/busy') so the description matches how users actually phrase requests.

Dimension	Reasoning	Score
Specificity	Quotes 'Google Calendar integration' and 'standalone OAuth authentication' — it names the domain but the only action word is the generic 'integration', with no concrete operations (list/create/delete events) stated, matching the score-2 anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	The 'what' is vague ('integration with standalone OAuth authentication') and there is no 'when' / 'Use when...' clause at all, matching the score-2 anchor 'Has a vague what and no when'; the missing-trigger-clause rule also caps this at 3, and it sits below that cap.	2 / 5
Trigger Term Quality	'Google Calendar' is a strong natural term users would say, but common variations like 'events', 'schedule', 'appointments', or 'meetings' are absent, fitting the score-3 anchor 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Google Calendar' plus 'No MCP server required' carves a clear niche distinct from generic calendar/MCP skills with only minor overlap risk, matching the score-4 anchor 'Mostly distinct; minor overlap risk with closely related skills'.	4 / 5
	Total	11 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 27 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/google-calendar-automation/SKILL.md
Commit: 57c135b

Reviewed: 4 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.