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.
81
72%
Does it follow best practices?
Impact
98%
1.28xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/calendly-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 specifying concrete capabilities and is highly distinctive due to the Calendly/Composio niche. However, it lacks an explicit 'Use when...' clause and misses common natural language trigger terms users might say (e.g., 'book a meeting', 'schedule a call'). Adding these would significantly improve skill selection accuracy.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Calendly scheduling, booking meetings, checking availability, or managing calendar events.'
Include more natural user trigger terms such as 'book a meeting', 'schedule a call', 'time slots', 'booking link', and 'calendar availability'.
| 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
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 solid, highly actionable skill for Calendly automation that provides clear tool sequences, specific parameters, and important pitfalls for each workflow. Its main weakness is verbosity through repetition—URI format warnings, pagination patterns, and scope requirements are restated across multiple sections. The content would benefit from consolidation of repeated information and potentially splitting detailed reference material into separate files.
Suggestions
Consolidate repeated pitfalls (URI formats, pagination, scope requirements) into the 'Common Patterns' and 'Known Pitfalls' sections only, removing duplicates from individual workflow pitfall lists to reduce token usage by ~30%.
Consider extracting the Quick Reference table and Known Pitfalls into a separate REFERENCE.md file, keeping SKILL.md focused on setup and core workflows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but quite verbose at ~200 lines. There's significant repetition—pitfalls about URI formats appear in individual workflows AND in the 'Known Pitfalls' section, pagination is explained multiple times, and the 'Common Patterns' section largely restates what was already covered. The instruction to always search tools first is also repeated. However, it avoids explaining basic concepts Claude would know. | 2 / 3 |
Actionability | The skill provides concrete tool names, specific parameter names and formats (e.g., exact URI patterns like `https://api.calendly.com/users/{uuid}`), exact timestamp formats, and clear tool sequences for each workflow. The quick reference table is highly actionable. While there's no executable code per se, this is an API/tool-calling skill where the guidance is specific enough to be directly executable. | 3 / 3 |
Workflow Clarity | Each workflow has a clearly numbered tool sequence with labeled steps (Prerequisite/Required/Optional), explicit validation checkpoints (e.g., confirm connection is ACTIVE before proceeding, confirm event details before cancellation, get explicit user confirmation before destructive cancel operation), and detailed pitfalls sections that serve as error-prevention guidance. The cancel workflow appropriately includes confirmation steps before the irreversible action. | 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 to offload detailed content. The repeated pitfalls and common patterns sections could be separated into reference files. For a skill this long (~200 lines of substantive content), some content like the full quick reference table or detailed pitfalls could benefit from being in separate files. | 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 | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.