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.
75
65%
Does it follow best practices?
Impact
94%
1.59xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/google-calendar-automation/SKILL.mdQuality
Discovery
67%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 does well at listing specific capabilities and is clearly scoped to Google Calendar automation via a specific integration, making it distinctive. However, it lacks an explicit 'Use when...' clause which caps completeness, and the trigger terms could better reflect natural user language (e.g., 'book a meeting', 'schedule a call') rather than leaning on technical terminology like 'Rube MCP (Composio)'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to schedule meetings, check availability, book calendar events, or manage Google Calendar.'
Include more natural user trigger phrases such as 'book a meeting', 'schedule a call', 'when am I free', 'set up a recurring event' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create events, find free slots, manage attendees, and list calendars programmatically.' Also mentions 'scheduling, availability checks, and attendee management.' | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the capabilities listed. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'Google Calendar', 'events', 'scheduling', 'availability', 'attendees', 'free slots', but misses common user phrases like 'book a meeting', 'schedule a call', 'check my calendar', 'when am I free'. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to be used by users. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Google Calendar operations via a specific integration (Rube MCP/Composio). The combination of Google Calendar + specific tool makes it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%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-organized Google Calendar automation skill with excellent workflow clarity—the labeled tool sequences and explicit pitfall warnings are its strongest features. The main weaknesses are the lack of concrete invocation examples (showing actual tool calls with sample parameters) and notable content repetition, particularly around pitfalls and timezone handling. Trimming redundancy and adding 1-2 complete worked examples would significantly elevate this skill.
Suggestions
Add at least one complete worked example showing an actual tool invocation with real parameter values (e.g., a full GOOGLECALENDAR_CREATE_EVENT call with sample start_datetime, timezone, summary, and attendees).
Consolidate the repeated pitfalls—remove per-workflow pitfall entries that are duplicated verbatim in the 'Known Pitfalls' section, or vice versa, to reduce token usage by ~20%.
Consider extracting the Quick Reference table and detailed per-workflow parameter lists into a separate REFERENCE.md file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and provides genuinely useful information (pitfalls, parameter constraints), but there's significant repetition—the 'Known Pitfalls' section largely duplicates pitfalls already listed under each workflow, and some information is restated across sections (timezone handling, attendee email requirements). The quick reference table adds value but the overall document could be tightened by ~30%. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and format requirements (ISO 8601, IANA timezones), which is valuable. However, there are no concrete executable examples showing actual tool invocations with sample parameters—everything is described rather than demonstrated. A single complete example of creating an event with actual parameter values would significantly improve actionability. | 2 / 3 |
Workflow Clarity | Each workflow has a clear numbered tool sequence with explicit labels ([Prerequisite], [Required], [Optional], [Alternative], [Fallback]) that make the sequence and decision points unambiguous. The availability workflow includes a validation-like pattern (check free slots before booking). The attendee management workflow explicitly warns about the destructive PATCH behavior and prescribes searching first to get IDs. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table, but it's a monolithic document with no bundle files or references to separate detailed materials. The repeated pitfalls across sections and the inline quick reference table suggest content that could benefit from being split into separate reference files. For a skill of this length (~180 lines), some separation would improve navigability. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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
- davepoon/buildwithclaude
- Commit
74c7031
- 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.