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.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill google-calendar-automation80
Quality
72%
Does it follow best practices?
Impact
94%
1.59xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/google-calendar-automation/SKILL.mdDiscovery
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 effectively communicates specific capabilities for Google Calendar automation with good technical detail. However, it lacks explicit trigger guidance ('Use when...') and misses common natural language terms users might say when needing calendar help, such as 'meeting', 'book', or 'schedule a call'.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to create calendar events, check availability, or manage Google Calendar.'
Include more natural user terms like 'meeting', 'book time', 'schedule a call', 'calendar invite', 'when am I free' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create events, find free slots, manage attendees, and list calendars programmatically' along with 'scheduling, availability checks, and attendee management'. | 3 / 3 |
Completeness | Clearly answers 'what' with detailed capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Google Calendar', 'events', 'scheduling', 'availability', 'attendees', 'free slots', but missing common user variations like 'meeting', 'book time', 'calendar invite', 'schedule a call'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to 'Google Calendar' and 'Rube MCP (Composio)' which creates a distinct niche; unlikely to conflict with generic document or code skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent workflow clarity and concrete guidance. The tool sequences are well-documented with clear prerequisites and validation steps. Main weaknesses are some redundancy in pitfall documentation and a monolithic structure that could benefit from splitting detailed reference material into separate files.
Suggestions
Consolidate pitfalls into a single section or separate PITFALLS.md file to eliminate repetition across workflow sections
Move the Quick Reference table and Common Patterns to a separate REFERENCE.md file, keeping SKILL.md focused on core workflows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - pitfalls are repeated across sections and in a consolidated 'Known Pitfalls' section. The quick reference table duplicates information already covered in workflows. | 2 / 3 |
Actionability | Provides concrete tool names, specific parameter formats (ISO 8601, IANA timezones), exact parameter names, and clear examples of correct vs incorrect values. The quick reference table makes tool selection immediately actionable. | 3 / 3 |
Workflow Clarity | Each workflow has clear numbered sequences with explicit prerequisite/required/optional labels. Tool sequences are well-ordered with validation steps (e.g., confirm connection ACTIVE before proceeding, check availability before booking). | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in a single file. The extensive pitfalls and patterns sections could be split into separate reference files. The external toolkit docs link is good but underutilized. | 2 / 3 |
Total | 10 / 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 | |
- 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.