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.

78

1.61x
Quality

68%

Does it follow best practices?

Impact

100%

1.61x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

61%Weight 40%Scale 1-5

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

The body is well-structured and actionable with concrete tool slugs and parameters, but suffers from duplicated pitfall/reference content and lacks verification steps for destructive webhook/team operations. Trimming redundancy and adding validation would lift conciseness and workflow clarity.

Suggestions

Remove the duplicate date/time and event-type pitfalls from 'Known Pitfalls' since they are already covered in each workflow's Pitfalls section, or consolidate into one location.

Add an explicit verification step after destructive operations (e.g. re-list webhooks after DELETE to confirm removal; verify team creation by fetching the new team ID).

Consider moving the full parameter reference into a separate REFERENCE.md and keeping SKILL.md as an overview with one-level-deep links, to improve progressive disclosure and reduce redundancy.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete tool slugs and params, but the 'Known Pitfalls' section restates date/time format pitfalls already covered per-workflow, and the Quick Reference table duplicates the tool/param listings, adding avoidable tokens.

3 / 5

Actionability

Concrete tool slugs (e.g. CAL_FETCH_ALL_BOOKINGS), named parameters with formats (ISO 8601, IANA timezone), and enumerated event triggers give mostly executable guidance, though no full example argument payloads are provided.

4 / 5

Workflow Clarity

Sequences are clear and Setup includes an ACTIVE-status validation checkpoint, but destructive operations (webhook deletion, team creation) lack verification steps, so workflow clarity is capped at 3 per the destructive-operation rule.

3 / 5

Progressive Disclosure

Well-organized into Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, and Quick Reference with clear navigation, but all content is inline in a single ~200-line file with no progressive layering or deeper references.

4 / 5

Total

14

/

20

Passed

Description

75%Weight 40%Scale 1-5

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, distinctive, and names four concrete capabilities, but it omits an explicit 'Use when...' trigger clause, which caps completeness. Adding a trigger phrase would likely raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause such as 'Use when the user wants to schedule or manage Cal.com bookings, check availability, set up webhooks, or manage teams.'

Add natural synonyms users say ('scheduling', 'calendar appointments', 'meeting slots') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'manage bookings, check availability, configure webhooks, and handle teams' — giving comprehensive coverage of the Cal.com automation surface, matching the score-5 anchor.

5 / 5

Completeness

The 'what' is clear (automate Cal.com tasks with four named operations) but there is no explicit 'Use when...' trigger clause, so completeness is capped at 3 per the missing-trigger-guidance rule.

3 / 5

Trigger Term Quality

Includes natural domain terms ('Cal.com', 'bookings', 'availability', 'webhooks', 'teams') a user would say, but misses common synonyms like 'scheduling', 'calendar', or 'appointments', placing it just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to 'Cal.com tasks via Rube MCP (Composio)' with distinct, niche-specific triggers, giving minimal overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.