google-calendar-automation

Automate Google Calendar events, scheduling, availability checks, and attendee management via Rube MCP (Composio). Create events, find free slots, manage attendees, and list calendars programmatically.

1.59x

Quality

73%

Does it follow best practices?

Impact

94%

1.59x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

61%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 dense, well-structured operational reference with concrete tool sequences, parameters, and pitfalls that make it highly actionable for an MCP-driven skill. Its weaknesses are duplicated pitfall content (token cost), and absent validation checkpoints around destructive operations (delete event, PATCH attendees), which the rubric caps.

Suggestions

Cut or collapse the "Known Pitfalls" section: nearly every bullet duplicates a pitfall already stated under its workflow (natural-language dates, timezone, duration limit, attendee emails, PATCH-replaces-attendees, Meet fallback), saving ~10 lines of tokens.

Add validation checkpoints around destructive operations: confirm with the user (or re-find the event and show it) before `DELETE_EVENT`, and read the current attendee list before `PATCH_EVENT` so the replacement list is verified to include existing attendees.

Include one complete example tool call payload (e.g., a full `GOOGLECALENDAR_CREATE_EVENT` argument set) so the common case is copy-paste ready, and consider moving the per-tool parameter reference into a references/ file to slim SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is terse and reference-style (tool slugs, parameter names, pitfalls) with no padding explaining concepts Claude already knows, but the "Known Pitfalls" section ("Natural language dates: NOT supported", "event_duration_minutes max 59", "PATCH replaces attendees", etc.) restates roughly nine pitfalls already given verbatim in the per-workflow sections, and the intro paragraph repeats the frontmatter description. This is "mostly efficient but could be tightened" rather than the 4 anchor's minor trims.	3 / 5
Actionability	Concrete tool slugs (`GOOGLECALENDAR_CREATE_EVENT`, `GOOGLECALENDAR_FIND_EVENT`), exact parameter names and constraints (`event_duration_minutes` 0-59, `calendar_id`: 'primary'), value examples ('2026-01-19T00:00:00-08:00', 'America/New_York'), and an ID-resolution pattern section give mostly executable guidance. It falls short of the 5 anchor because no complete example tool-call payloads are shown for the common cases.	4 / 5
Workflow Clarity	Each workflow is clearly sequenced with Prerequisite/Required/Optional/Alternative labels and Setup includes a checkpoint ("Confirm connection status shows ACTIVE before running any workflows"), but destructive operations — `DELETE_EVENT` and `PATCH_EVENT` (whose attendees field "replaces entire attendees list") — have no validation/verification steps before or after execution. Per the rubric guideline, missing validation in destructive workflows caps workflow clarity at 3, which takes precedence over the otherwise strong sequencing.	3 / 5
Progressive Disclosure	No bundle files exist and the body references only one clearly signaled external link (composio.dev/toolkits/googlecalendar) with no nested references; sections are well organized with a Quick Reference table. However, at ~175 lines the per-tool parameter and pitfall reference is fully inlined where a separate reference file could carry the bulk, matching "good structure; minor organization gaps" rather than content appropriately split across files.	4 / 5
	Total	14 / 20 Passed

Description

75%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 specific, actionable, and clearly scoped to Google Calendar automation via Rube MCP, with strong distinctiveness. Its one structural weakness is the absence of any 'Use when...' trigger clause, which caps completeness and leaves invocation guidance implicit.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to create, find, or manage calendar events, check availability, or manage attendees in Google Calendar."

Include a few natural synonyms users actually say — "meetings", "book a time", "appointments", "invites" — alongside the current trigger terms.

State the Rube MCP prerequisite in terms of the user-facing situation (e.g. "requires a connected Google account") rather than only the tooling name.

Dimension	Reasoning	Score
Specificity	"Automate Google Calendar events, scheduling, availability checks, and attendee management" plus "Create events, find free slots, manage attendees, and list calendars" lists multiple specific concrete actions with comprehensive coverage of the calendar-automation domain. It exceeds the 4 anchor because there are no meaningful gaps in capability coverage.	5 / 5
Completeness	The "what" is explicit and concrete (event creation, free slots, attendee management, listing calendars), but there is no "Use when..." clause or any equivalent explicit trigger guidance; per the rubric guideline, a missing 'when' clause caps completeness at 3. It is not a 4 because that anchor requires both 'what' and 'when' to be present.	3 / 5
Trigger Term Quality	Natural phrases like "Google Calendar", "events", "scheduling", "availability checks", "find free slots", and "manage attendees" are present and would be said by users, but common synonyms such as "meetings", "book", "appointments", or "invites" are missing. This matches "good keyword coverage; a few natural terms missing" rather than the 5 anchor's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	"Google Calendar ... via Rube MCP (Composio)" names a single specific product domain with distinct triggers (Google Calendar, events, free slots), giving it a clear niche with minimal conflict risk against other skills. It fits the 5 anchor rather than 4's "minor overlap risk with closely related skills".	5 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/google-calendar-automation/SKILL.md
Commit: 10bfc43

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