calendly-automation

Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.

1.28x

Quality

76%

Does it follow best practices?

Impact

98%

1.28x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/calendly-automation/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.

A dense, highly actionable skill body that gives exact MCP tool sequences, parameter formats, and pitfalls without padding. The destructive cancel workflow is properly gated by explicit confirmation. Weaknesses are mild: some pitfall repetition across sections and no externalized reference file for the bulk tool table.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence — no explanation of what Calendly or MCP is — and nearly every token carries API-specific detail. Not 5 because the full-URI/"not me" rule is stated three times (workflow 1 pitfalls, ID Resolution, Known Pitfalls) and pagination guidance is repeated across sections.	4 / 5
Actionability	Fully executable guidance: exact tool slugs, numbered sequences tagged [Prerequisite]/[Required]/[Optional], parameter formats with concrete example values (e.g. `https://api.calendly.com/users/{uuid}`, `2024-01-01T00:00:00.000000Z`), and a quick-reference table covering every common case. Nothing is vague or pseudocode.	5 / 5
Workflow Clarity	Setup has explicit validation checkpoints ("Confirm connection status shows ACTIVE before running any workflows"), the destructive cancel workflow requires explicit user confirmation, and pagination loops are defined ("loop until page_token is absent"). Not 5 because error recovery (403 handling) is noted but not proceduralized, and there is no post-action verification after cancel or scheduling-link creation.	4 / 5
Progressive Disclosure	No bundle files exist, so a single well-sectioned SKILL.md is appropriate, and headers/tables make navigation easy. Not 5 because at ~208 lines the monolithic layout inlines bulk reference material (the 17-row quick-reference table and Known Pitfalls section) that could live in a separate references file; not 3 because structure is good and no reference is buried or nested.	4 / 5
	Total	17 / 20 Passed

Description

70%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.

A strong, specific description of the Calendly automation niche that clearly states what it does and stays appropriately concise. Its main defect is the absence of any "Use when..." trigger clause, which caps completeness and weakens its ability to fire at the right moments.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Calendly, booking or canceling appointments, checking availability, or managing scheduled events."

Include natural synonyms users would actually say ("appointments", "meetings", "booking links") alongside the current domain terms.

Make the action list slightly more concrete (e.g. "list and cancel events, track invitees, create single-use scheduling links") to replace the generic 'event management' and 'organization administration' phrasing.

Dimension	Reasoning	Score
Specificity	Lists five named action areas ("scheduling, event management, invitee tracking, availability checks, and organization administration"), giving several specific actions with only minor gaps. Not 5 because 'event management' and 'organization administration' remain domain-generic rather than concrete operations, unlike anchor 5's fully concrete action list.	4 / 5
Completeness	The 'what' is clear and concrete, but the description contains no "Use when..." clause or equivalent explicit trigger guidance, which the judging guidelines cap at 3. Not 2 because the 'what' is specific, not vague.	3 / 5
Trigger Term Quality	"Calendly" is the dominant natural trigger, well supported by "scheduling", "invitee", and "availability". Not 5 because common user phrasings like "appointment", "booking", or "meeting" are missing; not 3 because coverage goes well beyond a single generic keyword.	4 / 5
Distinctiveness Conflict Risk	"Calendly" combined with "via Rube MCP (Composio)" carves a clear niche with distinct triggers and minimal conflict risk against any other skill.	5 / 5
	Total	16 / 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: davepoon/buildwithclaude
Path: plugins/all-skills/skills/calendly-automation/SKILL.md
Commit: c9856ea

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