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.

1.61x

Quality

—

Does it follow best practices?

Impact

100%

1.61x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete tool and parameter details, but it is a single monolithic file with some internal redundancy and missing validation checkpoints around destructive operations.

Suggestions

Add explicit validation/confirmation steps for destructive operations (e.g. confirm a webhook exists and is intended for deletion before calling CAL_DELETE_WEBHOOK_BY_ID, and verify a booking-creation response before reporting success).

Extract the per-tool parameter reference and Quick Reference table into a separate REFERENCE.md, leaving SKILL.md as an overview + workflow guide, to reduce inline bulk.

Remove the standalone "Known Pitfalls" section that duplicates the per-workflow pitfalls, or consolidate all pitfalls there and drop the inline copies.

Dimension	Reasoning	Score
Conciseness	The body is dense API reference material without beginner-concept padding, but the consolidated "Known Pitfalls" section restates date/event-type/permission pitfalls already given inline and the Quick Reference table repeats tool slugs, so it could be tightened.	2 / 3
Actionability	Concrete tool slugs, exact parameter names, valid enum values (e.g. status 'upcoming'/'cancelled'), and exact formats (ISO 8601, IANA timezones) make the guidance specific and directly usable.	3 / 3
Workflow Clarity	Workflows are sequenced with [Required]/[Optional] tags and the setup has a validation checkpoint (confirm ACTIVE), but destructive operations like webhook deletion and booking creation lack explicit validate/confirm-then-proceed feedback loops, capping clarity at 2.	2 / 3
Progressive Disclosure	At ~210 lines with no bundle files, all reference content (params, pitfalls, quick-reference table) lives inline in SKILL.md; sections are well organized, but material that could be split into a separate reference file is kept inline.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 specific and distinctive, naming concrete Cal.com operations and natural trigger terms, but it omits an explicit "Use when..." clause that would lift completeness to the top level.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to automate Cal.com scheduling, bookings, availability, webhooks, or team management."

Move the procedural hint ("Always search tools first for current schemas") into the body so the description stays a pure what/when summary.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "manage bookings, check availability, configure webhooks, and handle teams" — matching the score-3 anchor of enumerating specific operations rather than vague language.	3 / 3
Completeness	It clearly states what the skill does but lacks an explicit "Use when..." trigger clause; the second sentence ("Always search tools first for current schemas") is procedural, not a usage trigger, so completeness is capped at 2 per the guidelines.	2 / 3
Trigger Term Quality	Natural terms a user would say (Cal.com, bookings, availability, webhooks, teams) are well covered; the technical "Rube MCP (Composio)" is supplementary rather than the only phrasing.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Cal.com via a specific MCP/Composio toolkit, giving it a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Commit: 366e45b

Reviewed: 2 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.