Name: calcom
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

calcom

Cal.com integration. Manage Users. Use when the user wants to interact with Cal.com data.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/calcom/SKILL.md

Quality

Content

82%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 highly actionable with executable CLI commands and a well-sequenced, state-aware connection workflow. The main weaknesses are minor verbosity in the intro and the inline action table, plus a lack of verification guidance for destructive booking operations.

Suggestions

Add a post-run verification step for destructive actions (e.g., re-fetch a booking after update/cancel to confirm the result) to close the workflow_clarity gap.

Trim the opening two-sentence description of what Cal.com is, since Claude can infer product context from the named integration.

Move the Popular actions table and category list into a one-level-deep reference file (e.g. ACTIONS.md) and link to it, improving progressive disclosure and token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with copy-paste CLI commands and only minor over-explanation (the opening two-sentence description of what Cal.com is), matching the "efficient; minor instances that could be trimmed" anchor; not a 5 because the intro paragraph and the 21-row "No description" action table carry some padding.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure/get, action list, action run with --input, request proxy) with flag tables, matching the fully-executable anchor; not lower because concrete examples cover the common cases comprehensively.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based checkpoints and a re-poll feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), matching the clear-sequence-with-most-checkpoints anchor; not a 5 because destructive actions like cancel-booking/update-booking are listed without any post-run verification step.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Working with Cal.com, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references and no bundle files present, matching the good-structure anchor; not a 5 because the bulky Popular actions table and category list are inlined rather than split into a one-level-deep reference file.	4 / 5
	Total	17 / 20 Passed

Description

66%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 correctly pairs a what/when structure in third person and is highly distinct thanks to the named product, but it is thin on concrete actions and natural trigger terms. Expanding the action list and trigger synonyms would lift the specificity and trigger_term_quality dimensions.

Suggestions

Expand "Manage Users" to name 2-3 more concrete actions (e.g., manage bookings, event types, and schedules) to improve specificity.

Add natural trigger synonyms users would say, e.g. "Use when the user wants to manage Cal.com bookings, scheduling, appointments, or event types."

Make the "when" clause more concrete with specific trigger phrases rather than the generic "interact with Cal.com data".

Dimension	Reasoning	Score
Specificity	Names the domain ("Cal.com integration") and one concrete action ("Manage Users"), matching the anchor for naming a domain plus 1-2 concrete actions; it is not a 2 because "Manage Users" is a concrete action rather than minimal/generic phrasing, and not a 4 because coverage is limited to a single action with no breadth (bookings, event types, schedules are omitted).	3 / 5
Completeness	Provides both a "what" ("Cal.com integration. Manage Users.") and an explicit "when" ("Use when the user wants to interact with Cal.com data."), satisfying the both-present anchor; not a 5 because the "when" is generic ("interact with Cal.com data") without concrete trigger phrases, and the "what" is thin given Cal.com's broader scope.	4 / 5
Trigger Term Quality	Includes the relevant product keyword "Cal.com" and "Cal.com data", but misses common natural variations users would say (bookings, scheduling, appointments, events), fitting the anchor for some relevant keywords missing common synonyms; not a 4 because the natural action phrases users actually utter are absent.	3 / 5
Distinctiveness Conflict Risk	Names a specific, distinct product (Cal.com) with a trigger scoped to that product's data, giving it a clear niche with minimal conflict risk; it is not a 4 because the named product itself removes the overlap risk that the "mostly distinct" anchor still allows.	5 / 5
	Total	15 / 20 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: membranedev/application-skills
Path: skills/calcom/SKILL.md
Commit: f484c82

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