google-calendar-automation

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

Quality

62%

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/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 clean, highly actionable CLI reference with excellent executable examples, but it lacks validation/confirmation steps around its destructive operations, which caps workflow clarity, and has no progressive-disclosure reference files for deeper material.

Suggestions

Add a validation/confirmation checkpoint before destructive commands, e.g. require listing the event and confirming before running delete-event.

Document an error-recovery flow for failed operations (auth errors, invalid EVENT_ID, calendar-not-found) with retry guidance.

Consider moving extended flag reference or troubleshooting into a references/ file and linking to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with copy-paste examples and minimal prose, assuming Claude's competence; it avoids explaining concepts Claude already knows, with only minor trimmable redundancy (the opening line repeats the frontmatter description), fitting the 'efficient; minor instances of over-explanation' anchor rather than the fully-lean level-5 example.	4 / 5
Actionability	Every operation is shown as fully executable, copy-paste-ready CLI commands with realistic flags and values covering the common cases (list, get, create, update, delete, find-free-time, respond), matching the level-5 anchor exactly.	5 / 5
Workflow Clarity	Operations are listed as discrete commands with a clear setup-to-usage sequence, but destructive/batch operations (delete-event, update-event, respond-to-event) have no validation or confirmation checkpoints, so per the judging guidelines workflow clarity is capped at 3 even though the commands themselves are clear.	3 / 5
Progressive Disclosure	Content is well organized into clear sections (First-Time Setup, Commands, Date/Time Format, Token Management) and is appropriately self-contained for a CLI reference, but there are no bundle/reference files to delegate detail to, so it sits at 'good structure; minor organization gaps' rather than the level-5 anchor that expects well-signaled one-level-deep references.	4 / 5
	Total	16 / 20 Passed

Description

48%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 is concise and identifies a clear niche, but it is generic about capabilities and omits any 'Use when...' trigger guidance, capping completeness and specificity. Adding concrete operations and explicit trigger phrases would lift it toward the top anchors.

Suggestions

Add concrete actions, e.g. 'Create, list, update, and delete calendar events, find free time, and respond to invitations'.

Append an explicit trigger clause such as 'Use when the user asks to manage Google Calendar events or check availability'.

Include natural synonyms like 'calendar', 'events', 'appointments', and 'scheduling' alongside 'Google Calendar'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Google Calendar integration') but the only action mentioned is generic ('integration with standalone OAuth authentication'), with no concrete operations like creating or listing events; matches the 'names the domain but actions are minimal or generic' anchor rather than the level-3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It states a clear 'what' (Google Calendar integration with standalone OAuth) but provides no 'when'/'Use when...' trigger guidance, so per the judging guidelines a missing trigger clause caps completeness at 3; it does not reach level 4 which requires both what and when.	3 / 5
Trigger Term Quality	'Google Calendar' is a natural keyword a user would say, but common variations and synonyms ('calendar', 'events', 'appointments', 'scheduling') are missing, fitting the 'some relevant keywords but missing common variations' anchor rather than the comprehensive level-5 example.	3 / 5
Distinctiveness Conflict Risk	The 'Google Calendar' niche and the 'No MCP server required' differentiator make it mostly distinct with only minor overlap risk against other calendar skills, fitting the level-4 anchor better than level 3 (which implies broader overlap) or level 5 (which expects explicit distinct trigger phrases).	4 / 5
	Total	12 / 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/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.