CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.61x
Quality

58%

Does it follow best practices?

Impact

100%

1.61x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/cal-com-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 solid structural framework for Cal.com automation with clear tool naming, workflow sequences, and parameter documentation. Its main weaknesses are redundancy across sections (date formats, parameters repeated in workflows and reference table), lack of executable examples with actual MCP call syntax, and missing validation/error-handling steps in workflows that involve creating or modifying resources. The content would benefit from being more concise and including concrete, copy-paste-ready examples.

Suggestions

Add concrete, executable MCP call examples with filled-in parameters (e.g., an actual RUBE_SEARCH_TOOLS call and a CAL_POST_NEW_BOOKING_REQUEST call with sample values) instead of plain-text numbered lists in Common Patterns.

Add explicit validation and error-handling steps to workflows—e.g., after booking creation, verify the response contains a booking ID; after webhook setup, describe how to confirm it's firing correctly.

Eliminate redundancy by removing the duplicated pitfalls from individual workflow sections and consolidating them in the Known Pitfalls section, or vice versa. Similarly, remove the parameter details from workflow sections since RUBE_SEARCH_TOOLS provides current schemas.

Consider splitting detailed parameter listings and pitfalls into a separate reference file to keep the main SKILL.md as a concise overview with quick-start guidance.

DimensionReasoningScore

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 sequences, which is good. However, there are no executable code examples or actual MCP call syntax—the 'Common Patterns' section uses plain text numbered lists rather than concrete call examples with parameters filled in. 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 lacks a validation step to confirm the booking was actually created successfully.

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 listings and pitfalls for each workflow could be split into separate reference files, with the main SKILL.md serving as a concise overview.

2 / 3

Total

8

/

12

Passed

Description

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 actions and carving out a distinct niche around Cal.com automation via a specific integration. However, it lacks an explicit 'Use when...' clause and misses common natural language trigger terms users might use like 'scheduling', 'calendar', or 'appointments', which limits its discoverability.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Cal.com scheduling, managing calendar bookings, or checking availability.'

Include natural user-facing trigger terms like 'calendar', 'scheduling', 'appointments', 'meeting slots' alongside the existing technical terms to improve discoverability.

DimensionReasoningScore

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 mention of Cal.com.

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'. 'Rube MCP (Composio)' is technical jargon users wouldn't naturally say.

2 / 3

Distinctiveness Conflict Risk

Very specific niche targeting Cal.com via Rube MCP (Composio). The combination of platform (Cal.com) and integration method (Rube MCP/Composio) makes it highly distinctive and unlikely to conflict with other skills.

3 / 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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
davepoon/buildwithclaude
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.