cal-com-automation
Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas.
72
58%
Does it follow best practices?
Impact
100%
1.61xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/cal-com-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 a good job listing specific capabilities and identifying a clear niche (Cal.com automation via Composio). However, it lacks an explicit 'Use when...' clause, which caps completeness, and it could benefit from more natural user-facing trigger terms like 'scheduling', 'calendar', or 'appointments' rather than relying on technical integration names.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Cal.com scheduling, booking management, or calendar availability.'
Include more natural trigger terms users would say, such as 'scheduling', 'calendar', 'appointments', 'meeting slots', or 'book a meeting'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'manage bookings, check availability, configure webhooks, and handle teams.' Also includes the operational instruction to 'search tools first for current schemas.' | 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 domain context. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Cal.com', 'bookings', 'availability', 'webhooks', and 'teams', but misses common user variations like 'calendar', 'scheduling', 'appointments', 'meeting slots', or 'Composio'. The term 'Rube MCP' is technical jargon unlikely to be used by most users. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Cal.com via Rube MCP (Composio), which is unlikely to conflict with other skills. The combination of platform (Cal.com) and integration method (Rube MCP/Composio) creates a clear, distinct identity. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive catalog of Cal.com operations via Rube MCP with clear tool names, parameter lists, and workflow sequences. Its main weaknesses are verbosity (especially redundant pitfalls and parameter documentation that duplicates what RUBE_SEARCH_TOOLS provides), lack of executable examples with actual MCP call syntax, and missing validation/error-recovery steps in workflows involving booking creation and webhook setup.
Suggestions
Add concrete, executable MCP call examples with sample parameter values (e.g., an actual RUBE_SEARCH_TOOLS call followed by a CAL_POST_NEW_BOOKING_REQUEST call with realistic inputs) instead of plain-text pseudocode.
Add explicit validation and error-recovery steps to workflows—e.g., check the booking creation response for errors, handle 'no available slots' gracefully, verify webhook delivery with a specific check.
Reduce redundancy by consolidating pitfalls into the single 'Known Pitfalls' section and removing per-workflow duplicates; also trim parameter lists since the skill instructs Claude to call RUBE_SEARCH_TOOLS for current schemas anyway.
Consider splitting detailed parameter references and pitfalls into a separate CAL_REFERENCE.md file, keeping SKILL.md as a concise overview with workflow sequences and quick reference table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but verbose in places—repeating pitfalls across sections (date formats mentioned multiple times), listing parameters that Claude could discover via RUBE_SEARCH_TOOLS (which the skill itself says to always call first), and the Known Pitfalls section largely duplicates per-workflow pitfalls. The quick reference table is useful but the overall document could be significantly tightened. | 2 / 3 |
Actionability | Tool names and parameter lists are concrete and specific, which is good. However, there are no executable code/command examples—the 'Common Patterns' section uses plain text pseudocode rather than actual MCP call syntax. The skill tells you what tools to call and what parameters to pass but doesn't show exact invocation examples with sample values. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps and labeled as Required/Optional. However, validation checkpoints are largely missing—the Booking Creation Flow doesn't include error handling for unavailable slots or failed bookings, webhook setup says 'verify webhook fires' without explaining how, and there are no explicit feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | The content is organized into logical sections with a quick reference table, which aids navigation. However, it's a long monolithic document (~180 lines of content) that could benefit from splitting detailed parameter lists and pitfalls into separate reference files. The external link to Composio docs is good but the skill itself doesn't split its own content across files. | 2 / 3 |
Total | 8 / 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
- Lingjie-chen/MT5
- Commit
3069d33
- 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.