Name: calendly
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

calendly

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

Quality

68%

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/calendly/SKILL.md

Quality

Content

75%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 concrete CLI commands and a clear connection workflow including state-based validation, weakened mainly by an unnecessary product-introduction paragraph and no verify step for destructive actions.

Suggestions

Remove or condense the introductory "Calendly is a scheduling automation tool..." paragraph since Claude already knows what Calendly is.

Add an explicit verification/check step before running destructive actions (cancel-event, delete-webhook-subscription), e.g. confirming the target UUID or listing before deleting.

Consider moving the full popular-actions table into a reference file and keeping only the most common entries inline to lighten the SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient with command snippets and tables, but the opening paragraph ("Calendly is a scheduling automation tool that eliminates the back-and-forth...") explains a product Claude already knows and could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection setup, action search/run, and proxy requests, plus a concrete actions table with keys and a JSON-input example covering the common cases.	5 / 5
Workflow Clarity	The connect-then-act flow is clearly sequenced with polling and state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but destructive actions like cancel-event and delete-webhook-subscription lack an explicit verify-before-run step, capping it below 5.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references, though everything is inlined in SKILL.md (e.g. the 15-row actions table) rather than split into reference files.	4 / 5
	Total	16 / 20 Passed

Description

61%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 has a clear, distinctive trigger tied to a named product and answers both what and when, but its capability list is thin and generic, listing only "Manage Users" while the skill does far more.

Suggestions

Replace the generic "Manage Users" with several concrete actions the skill supports, e.g. "List scheduled events, create scheduling links, and manage webhook subscriptions."

Add natural trigger synonyms users actually say, such as scheduling, booking meetings, or checking availability, alongside "interact with Calendly data".

Tighten the "when" clause to name concrete scenarios (e.g. booking demos, viewing busy times, setting up webhooks) rather than the generic "interact with Calendly data".

Dimension	Reasoning	Score
Specificity	The description names the domain ("Calendly integration") but only offers one minimal generic action ("Manage Users"), omitting the many concrete capabilities the skill actually supports (events, invitees, webhooks, scheduling links).	2 / 5
Completeness	Both a "what" ("Calendly integration. Manage Users.") and an explicit "when" ("Use when the user wants to interact with Calendly data") are present, though the "what" is narrow and the trigger could be more specific.	4 / 5
Trigger Term Quality	It includes the core keyword "Calendly" and a natural trigger ("Use when the user wants to interact with Calendly data") but misses common synonyms a user would say like scheduling, booking, meetings, or appointments.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Calendly" gives it a clear niche with a distinct trigger and minimal risk of firing for an unrelated skill.	5 / 5
	Total	14 / 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/calendly/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.