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 ./plugins/all-skills/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 is strong in specificity and distinctiveness, clearly naming the platform (Cal.com) and listing concrete actions like managing bookings and configuring webhooks. However, it lacks an explicit 'Use when...' clause and misses common natural language trigger terms users might say (e.g., 'scheduling', 'appointments', 'calendar'). Adding these would make it significantly more effective for skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Cal.com scheduling, booking management, or calendar availability.'
Include natural language trigger terms users would say, such as 'scheduling', 'appointments', 'calendar', 'meeting slots', and 'book a time'.
| 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 capability listing. | 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 technical term 'Rube MCP' is jargon most users wouldn't naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform reference 'Cal.com' and the tooling context 'Rube MCP (Composio)'. Unlikely to conflict with other skills given the narrow, well-defined niche. | 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 solid coverage of Cal.com operations via Rube MCP with clear tool names and workflow sequences. Its main weaknesses are redundant content (date format pitfalls repeated multiple times, parameter lists duplicated in workflows and quick reference), lack of executable examples, and missing validation/error-handling steps in workflows. The skill would benefit from being more concise and adding concrete invocation syntax.
Suggestions
Remove duplicated pitfalls (e.g., date formats) by consolidating them in the Known Pitfalls section only, and reference that section from individual workflows.
Add concrete MCP call examples with actual tool invocation syntax rather than pseudocode numbered lists in the Common Patterns section.
Add explicit validation checkpoints and error handling to workflows—e.g., 'If CAL_POST_NEW_BOOKING_REQUEST returns an error, check that the slot is still available and eventTypeId is valid before retrying.'
Consider removing the detailed parameter listings since the skill already instructs to call RUBE_SEARCH_TOOLS for current schemas—or keep only the non-obvious parameters and pitfalls.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but includes redundant information across sections. Pitfalls are repeated (date formats mentioned in individual workflows AND in the Known Pitfalls section), and some parameter listings are verbose given that the skill itself says to always call RUBE_SEARCH_TOOLS first for current schemas. The quick reference table at the end duplicates information already covered in each workflow section. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and tool sequences, which is good. However, there are no executable code examples or actual MCP call syntax—the 'Common Patterns' section uses pseudocode-style numbered lists rather than concrete invocation examples. The guidance is specific enough to follow but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps and labeled as Required/Optional. However, validation checkpoints are largely missing—there's no explicit error handling, no 'if this fails, do X' feedback loops for booking creation failures, webhook verification, or connection issues beyond the initial setup. The booking creation flow mentions checking availability first but doesn't include validation of the response. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a logical progression from setup to workflows to reference. However, with no bundle files, all content is inline in a single long document (~180 lines). The detailed parameter lists and pitfalls for each workflow could be split into separate reference files, and the quick reference table adds bulk that could be a separate cheat sheet. | 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
- 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.