CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

1.59x
Quality

63%

Does it follow best practices?

Impact

94%

1.59x

Average score across 3 eval scenarios

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 skill body is well-organized and actionable, with concrete tool sequences and a useful quick-reference table. Its main gaps are redundant pitfall repetition across sections and missing explicit validation checkpoints before destructive operations like event deletion and attendee replacement.

Suggestions

Add explicit validation steps before destructive actions (e.g. 'Confirm event_id matches the intended event before DELETE_EVENT'; 'Verify the full attendees list before PATCH_EVENT since it replaces the entire list').

Consolidate repeated timezone/duration pitfalls into the 'Known Pitfalls' section and cross-reference rather than restating in each workflow.

Include at least one fully-populated example tool call (with key arguments) for the most common task (create event) to make guidance copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-organized workflows and pitfalls, but it repeats guidance (timezone and duration pitfalls appear in multiple sections plus 'Known Pitfalls') and could be tightened by consolidating the redundancy.

3 / 5

Actionability

Concrete tool slugs, exact parameter formats (ISO 8601, IANA timezones, RFC3339 with offsets), and a quick-reference table give mostly executable guidance, though it lacks copy-paste-ready call examples with full argument payloads.

4 / 5

Workflow Clarity

Sequences are clearly listed with prerequisite/required tags, but workflows involving destructive operations (delete event, replace-attendee patch) lack explicit validation checkpoints confirming the correct event_id or attendee list before acting.

3 / 5

Progressive Disclosure

Content is well-structured into prerequisites, four core workflows, common patterns, known pitfalls, and a quick-reference table with one external link to toolkit docs; no bundle files exist, so the single-file organization is appropriate with only minor inline bulk.

4 / 5

Total

14

/

20

Passed

Description

66%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 strong on specificity and distinctiveness, clearly enumerating concrete calendar automation actions tied to a specific MCP toolkit. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and limits natural trigger-term coverage.

Suggestions

Add an explicit trigger clause such as 'Use when the user wants to schedule, reschedule, or manage Google Calendar events, check availability, or add/remove attendees.'

Include natural user-facing phrasings (e.g. 'book a meeting', 'find a time', 'invite attendees') to improve trigger-term coverage.

Mention common synonyms/file-context cues if any apply to reduce overlap ambiguity with related scheduling skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Create events, find free slots, manage attendees, and list calendars programmatically') covering creation, scheduling, availability, and management — comprehensive coverage of the calendar domain.

5 / 5

Completeness

It clearly answers 'what' with specific actions but lacks an explicit 'Use when...' clause describing when Claude should invoke it, so the 'when' is only weakly implied — capping completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Relevant keywords like 'events', 'scheduling', 'availability checks', and 'attendee management' are present, but common natural phrasings users would say (e.g. 'schedule a meeting', 'book a slot', 'check my calendar', 'invite someone') and synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

The Rube MCP / Composio Google Calendar niche is fairly distinct from generic calendar skills, though minor overlap risk exists with broader scheduling or Gmail-related attendee skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
Reviewed

Table of Contents

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.