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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/google-calendar-automation/SKILL.md

Quality

Content

76%Scale 1-5

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

This is a well-structured CLI reference skill that excels in actionability with comprehensive, copy-paste ready examples for all operations. Its main weakness is the absence of validation or verification steps for destructive operations (delete, update), and no error handling guidance. The content is appropriately concise and well-organized for its purpose as a command reference.

Suggestions

Add verification steps after destructive operations (e.g., 'After deleting, run list-events to confirm removal' or 'After updating, run get-event EVENT_ID to verify changes')

Add a brief error handling section covering common failures (e.g., expired auth, invalid event ID, permission denied) and how to recover from them

Dimension	Reasoning	Score
Conciseness	The content is efficient and avoids explaining what Google Calendar or OAuth is. The examples are practical and not padded. Minor verbosity in showing every possible flag combination for each command, but this serves as a useful reference. The Date/Time Format and Calendar ID Format sections are borderline unnecessary for Claude but brief enough.	4 / 5
Actionability	Every command is fully executable with copy-paste ready examples covering common use cases. The CLI interface is clearly documented with concrete flags, arguments, and realistic example values. Multiple variations are shown for each command covering the key scenarios.	5 / 5
Workflow Clarity	The setup flow (auth → commands) is clear, and individual commands are well-documented. However, there are no validation or verification steps after destructive operations like delete-event or update-event. The delete operation has no confirmation or undo guidance. For a skill that includes destructive operations (delete, update), the lack of validation/feedback loops caps this at 3.	3 / 5
Progressive Disclosure	The content is well-structured with clear section headers and logical grouping (Setup → Commands → Reference info). For a CLI reference skill of this size (~120 lines), the inline approach is appropriate. Minor improvement could be made by noting where the scripts live or referencing any error handling documentation, but overall the organization is good.	4 / 5
	Total	16 / 20 Passed

Description

39%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 identifies the domain (Google Calendar) clearly but fails to specify any concrete actions the skill can perform and lacks a 'when to use' clause entirely. It spends valuable space on implementation details (OAuth, no MCP server) that don't help Claude decide when to select this skill over others.

Suggestions

Add concrete actions the skill performs, e.g., 'Creates, reads, updates, and deletes Google Calendar events, lists upcoming events, and checks availability.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about their calendar, scheduling meetings, checking availability, creating events, or mentions Google Calendar/gcal.'

Replace implementation details ('standalone OAuth', 'No MCP server') with user-facing capability descriptions—implementation details don't help with skill selection.

Dimension	Reasoning	Score
Specificity	Names the domain (Google Calendar) but describes no concrete actions. 'Integration' is vague—it doesn't specify whether it creates events, reads calendars, deletes events, etc. The mention of 'standalone OAuth authentication' is an implementation detail, not a user-facing capability.	2 / 5
Completeness	The 'what' is vague ('integration' with no specific actions listed), and there is no 'when' clause at all. The description focuses on implementation details (OAuth, no MCP server) rather than answering what it does or when to use it.	2 / 5
Trigger Term Quality	'Google Calendar' is a strong natural keyword users would say. However, it misses common variations like 'calendar events', 'schedule', 'meeting', 'appointment', 'gcal', which are terms users would naturally use when needing this skill.	3 / 5
Distinctiveness Conflict Risk	'Google Calendar' is a fairly distinct domain that wouldn't easily conflict with most other skills. The mention of 'No MCP server required' even distinguishes it from potential MCP-based calendar integrations. Minor overlap risk with general scheduling or calendar skills.	4 / 5
	Total	11 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/google-calendar-automation/SKILL.md
Commit: fbdfd63

Reviewed: about 18 hours 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.