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

65%

Does it follow best practices?

Impact

94%

1.59x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/google-calendar-automation/SKILL.md

Quality

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 particular 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 calendar availability, book time slots, or manage Google Calendar events.'

Include more natural user-facing trigger terms like 'book a meeting', 'schedule a call', 'when am I free', 'set up a meeting', 'calendar invite' to improve matching against real user requests.

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', 'set up a meeting'. 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 solid instructional skill with excellent workflow clarity — clear sequencing, labeled step types, and good pitfall documentation. Its main weaknesses are redundancy across sections (pitfalls repeated in both per-workflow and summary sections) and the lack of concrete, executable tool call examples that would make it immediately actionable. The content would benefit from trimming duplicated information and adding at least one complete example invocation per core workflow.

Suggestions

Add at least one concrete, copy-paste-ready tool call example per core workflow (e.g., a full GOOGLECALENDAR_CREATE_EVENT call with realistic parameters) to improve actionability.

Remove or consolidate the 'Known Pitfalls' summary section since nearly all items are already covered in per-workflow pitfall blocks — this would significantly improve conciseness.

Consider splitting the quick reference table and detailed workflow sections into a separate reference file, keeping SKILL.md as a concise overview with links to details.

Dimension	Reasoning	Score
Conciseness	The skill is fairly well-organized but has significant redundancy — the 'Known Pitfalls' section largely repeats pitfalls already listed under each workflow section. The quick reference table also duplicates information. Some trimming would improve token efficiency without losing clarity.	2 / 3
Actionability	The skill provides clear tool names, parameter names, and specific format requirements (ISO 8601, IANA timezones), which is good. However, there are no concrete executable examples showing actual tool calls with sample parameters — everything is described abstractly rather than demonstrated with copy-paste-ready invocations.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional, Alternative, Fallback). The setup section includes a verification checkpoint (confirm ACTIVE status before proceeding), and the attendee management workflow explicitly warns about the destructive PATCH behavior with a clear mitigation strategy.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections and a quick reference table, but it's quite long (~200 lines) and could benefit from splitting detailed workflow sections or the pitfalls/reference table into separate files. The external link to Composio docs is present but there are no internal file references for deeper content.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 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: Lingjie-chen/MT5
Commit: 3069d33

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