calendly-automation

Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.

1.28x

Quality

65%

Does it follow best practices?

Impact

98%

1.28x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/calendly-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 specifying concrete capabilities and is highly distinctive due to the Calendly/Composio niche. However, it lacks an explicit 'Use when...' clause that would help Claude know when to select this skill, and it could benefit from more natural user-facing trigger terms like 'book a meeting' or 'schedule a call'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Calendly, booking meetings, scheduling calls, checking availability, or managing calendar invites.'

Include more natural user trigger terms such as 'book a meeting', 'schedule a call', 'time slots', 'booking link', and 'calendar availability' to improve matching against common user requests.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: scheduling, event management, invitee tracking, availability checks, and organization administration. Also specifies the tool/platform (Calendly via Rube MCP/Composio).	3 / 3
Completeness	Clearly answers 'what does this do' with specific Calendly automation capabilities, but lacks an explicit 'Use when...' clause. The instruction to 'always search tools first' is operational guidance, not a trigger condition. Per rubric, missing 'Use when' caps completeness at 2.	2 / 3
Trigger Term Quality	Includes good keywords like 'Calendly', 'scheduling', 'event management', 'invitee', 'availability', but misses common user variations like 'book a meeting', 'calendar link', 'schedule a call', 'time slots', or 'booking'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific mention of 'Calendly' and 'Rube MCP (Composio)'. This is unlikely to conflict with other skills since it targets a very specific platform and integration method.	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 Calendly automation skill with clear workflow sequences, good pitfall documentation, and a useful quick reference table. Its main weaknesses are redundancy across sections (URI warnings, pagination notes repeated multiple times), lack of concrete executable examples showing actual tool call payloads, and all content being inline rather than using progressive disclosure to separate overview from detailed reference material.

Suggestions

Add at least one concrete tool call example per workflow showing actual input parameters and expected response structure (e.g., a real RUBE_SEARCH_TOOLS call with calendly toolkit and the response format).

Consolidate repeated pitfalls (URI format, pagination, scope requirements) into the Common Patterns section only, and reference that section from individual workflows instead of restating.

Split detailed workflow sections and the quick reference table into separate referenced files (e.g., WORKFLOWS.md, REFERENCE.md) to make the main SKILL.md a concise overview with navigation links.

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes some redundancy — pitfalls are repeated across sections (URI format warnings appear in nearly every workflow and again in Known Pitfalls), and the Common Patterns section largely restates information already covered in individual workflows. The quick reference table adds value but the overall document could be tightened by ~30%.	2 / 3
Actionability	Tool sequences are clearly named and ordered with specific parameter names and example URI formats, which is good. However, there are no executable code snippets or concrete tool call examples showing actual input/output JSON. The guidance stays at the 'describe the parameters' level rather than providing copy-paste-ready tool invocations.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with labeled steps (Prerequisite/Required/Optional), explicit validation checkpoints (e.g., confirm connection is ACTIVE before proceeding, confirm event details before cancellation, get user confirmation before destructive cancel operation), and error recovery guidance (check existing invitations before creating duplicates, handle 403 errors).	3 / 3
Progressive Disclosure	The content is well-structured with clear sections and a useful quick reference table, but it's a monolithic ~200-line document with no references to separate files for detailed workflows or advanced topics. The Common Patterns and Known Pitfalls sections could be split out, and individual workflow details could be in separate files with the SKILL.md serving as an overview.	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.