googlecalendar-automation
by ComposioHQgooglecalendar-automation helps Claude automate Google Calendar via Composio Rube MCP by verifying an ACTIVE connection, searching current tool schemas first, and then creating, finding, or updating events safely.
This skill scores 68/100, which makes it acceptable but limited for directory listing. Directory users get enough information to understand that it automates Google Calendar through Composio's Rube MCP and how to start with connection and tool discovery, but the listing should be treated as a lightweight routing/workflow wrapper rather than a fully documented calendar automation playbook.
- Frontmatter is valid and clearly names the MCP dependency: `requires: mcp: [rube]`.
- Prerequisites and setup explain that Rube MCP must be connected, Google Calendar must be active via `RUBE_MANAGE_CONNECTIONS`, and `RUBE_SEARCH_TOOLS` should be called first.
- The skill gives a reusable execution pattern centered on discovering current Google Calendar tool schemas before acting, which can reduce stale-tool guesswork.
- No support files, examples, scripts, or README are present beyond SKILL.md, so adoption depends entirely on the short in-skill instructions.
- The workflow is intentionally schema-discovery driven and does not provide concrete Google Calendar tool calls for common tasks such as creating, updating, or listing events.
Overview of googlecalendar-automation skill
What googlecalendar-automation does
googlecalendar-automation is a Claude skill for automating Google Calendar work through Composio’s Rube MCP Google Calendar toolkit. It is designed for agents that need to discover available Google Calendar tools, confirm the user’s calendar connection, and then create, search, update, or coordinate calendar operations with the current tool schemas instead of guessing API fields.
Best fit for Workflow Automation users
The googlecalendar-automation skill is most useful when Google Calendar is part of a broader Workflow Automation task: scheduling meetings, checking availability, finding events, updating recurring plans, or coordinating calendar changes from natural-language instructions. It fits teams already using MCP-enabled clients and Composio/Rube, especially when they want Claude to operate against live Google Calendar tools rather than produce manual instructions.
Key differentiator: search tools first
The important behavior is not just “use Google Calendar.” The skill explicitly requires the agent to call RUBE_SEARCH_TOOLS first, because Rube tool schemas can change and task-specific tool recommendations matter. This reduces failures caused by stale field names, unsupported parameters, or assuming a Google Calendar API shape that the active Composio tool does not expose.
What to check before installing
This skill has a compact repository footprint: the main file is SKILL.md, with no extra scripts, references, rules, or README in the skill folder. That makes it easy to inspect, but it also means adoption depends on your Rube MCP setup and Google Calendar connection being correct. If you are not using Rube MCP, this is not a standalone calendar automation library.
How to Use googlecalendar-automation skill
googlecalendar-automation install and setup path
Install from the source repository with your skill manager, for example:
npx skills add ComposioHQ/awesome-claude-skills --skill googlecalendar-automation
Then open composio-skills/googlecalendar-automation/SKILL.md first. The skill requires an MCP server named through Rube, with https://rube.app/mcp added in your client configuration. Before asking Claude to manipulate calendars, verify that RUBE_SEARCH_TOOLS is available and that RUBE_MANAGE_CONNECTIONS can show an ACTIVE connection for toolkit googlecalendar.
Inputs the skill needs to work well
A weak request is: “Schedule a meeting tomorrow.” A stronger prompt gives the agent enough context to choose the right Google Calendar tool and avoid destructive changes:
- calendar account or calendar name, if not the default
- event title and purpose
- date, time range, timezone, and duration
- attendees and whether invites should be sent
- location or conferencing preference
- recurrence rules, reminders, or visibility
- whether to create a new event, update an existing event, or search first
- confirmation rules before changing or deleting events
Example: Use googlecalendar-automation to find an open 30-minute slot next Tuesday between 10:00 and 15:00 Europe/London for Alice and me, then draft the event details before creating it. Search Rube tools first and confirm the calendar connection is ACTIVE.
Practical googlecalendar-automation usage workflow
A reliable googlecalendar-automation usage pattern is:
- Ask Claude to invoke the skill for a specific calendar job.
- Require tool discovery with
RUBE_SEARCH_TOOLSfor that exact use case, not a generic search. - Confirm the Google Calendar connection with
RUBE_MANAGE_CONNECTIONS. - Have Claude summarize the intended action before execution when the task changes live calendar data.
- Execute the selected Rube tool using the discovered schema.
- Ask for a short result summary: event ID, title, time, attendees, and any warnings.
This workflow is especially important for updates and deletions. Calendar state changes are user-visible, and a mistaken match can affect real attendees.
Repository files to read first
Start with SKILL.md; it contains the whole operational contract: prerequisites, Rube setup, tool discovery, and the core workflow pattern. There are no supporting rules/, resources/, references/, or scripts/ folders in the skill path, so do not expect hidden examples or helper code. If you need deeper API behavior, use the toolkit docs linked from the skill: composio.dev/toolkits/googlecalendar.
googlecalendar-automation skill FAQ
Is googlecalendar-automation a Google Calendar API wrapper?
No. It is a skill that guides Claude to use Google Calendar through Rube MCP and Composio’s toolkit. It does not provide a local SDK, REST client, or reusable code module. Its value is in enforcing the right agent workflow: discover tools, verify connection, then execute with the current schemas.
Why not use an ordinary prompt?
A normal prompt may tell Claude to “create a calendar event,” but it may skip connection checks or invent tool parameters. The googlecalendar-automation skill adds a repeatable operating pattern around RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS, which is useful when the available tool names and input fields must be discovered at runtime.
Is this suitable for beginners?
Yes, if your client already supports MCP and you can add the Rube MCP endpoint. Beginners who have never configured MCP may need to set that up first. The skill itself is short, but the real dependency is having an ACTIVE Google Calendar connection through Rube before asking Claude to perform calendar actions.
When should I not use this skill?
Do not use googlecalendar-automation if you need offline calendar generation, direct Google API programming, CalDAV integration, or a custom backend service. It is also a poor fit for highly regulated workflows unless your organization has reviewed Composio/Rube access, OAuth permissions, logging, and approval requirements for modifying calendar data.
How to Improve googlecalendar-automation skill
Improve prompts for googlecalendar-automation
Better prompts reduce wrong-calendar and wrong-time errors. Include timezone, calendar scope, attendees, and confirmation policy. For example, say: Search my primary calendar for events matching "QBR prep" next week, list candidates first, and do not update anything until I choose one. This gives the agent a safe search-first path instead of forcing it to infer which event should be changed.
Handle common failure modes
The most common blockers are missing Rube MCP access, inactive Google Calendar authorization, stale assumptions about tool fields, vague event matching, and ambiguous time language such as “Friday afternoon.” Fix them by requiring: active connection verification, fresh RUBE_SEARCH_TOOLS discovery, ISO-style dates where possible, explicit timezone, and a confirmation step before edits or cancellations.
Iterate after the first result
After the first output, ask for a concise execution audit: which Rube tool was selected, what schema fields were used, what calendar object was affected, and whether any attendees were notified. If the result is not right, correct the smallest missing input rather than rewriting the whole task. For example: Same event, but use America/New_York and add a 10-minute reminder.
Extend the skill for team use
If your team uses googlecalendar-automation for Workflow Automation regularly, consider adding local guidance around approval thresholds, naming conventions, default calendars, meeting templates, and no-delete policies. The upstream skill is intentionally minimal; team-specific rules can make it safer without changing the core requirement to search Rube tools first.