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

69%

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

63%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 skill body is well-structured and actionable with clear workflow sequencing and proper destructive-operation confirmation, but it is somewhat repetitive and keeps all reference material inline in a single file rather than progressively disclosing it.

Suggestions

Move the Quick Reference table and the consolidated Known Pitfalls into a separate references/ file (e.g. REFERENCE.md) and link to it from the body to improve progressive disclosure.

De-duplicate the 'never use "me"' / URI-format pitfalls that appear in both per-workflow 'Pitfalls' blocks and the 'Known Pitfalls' section.

Add one or two copy-paste tool-call examples (e.g. a sample RUBE_SEARCH_TOOLS / CALENDLY_LIST_EVENTS request) to push actionability to fully executable.

Dimension	Reasoning	Score
Conciseness	The body is dense and free of concept-explanation padding, but pitfalls are repeated in multiple places (per-workflow 'Pitfalls', a 'Known Pitfalls' section, and 'Common Patterns') and the Quick Reference table re-lists tools already enumerated, so it could be tightened.	3 / 5
Actionability	Concrete tool slugs, exact parameter names, and example values ('https://api.calendly.com/users/{uuid}', '2024-01-01T00:00:00.000000Z') with [Prerequisite]/[Required]/[Optional] tags give mostly executable guidance, though there are no copy-paste tool-call examples.	4 / 5
Workflow Clarity	Workflows are clearly sequenced with numbered tool steps and explicit confirmation checkpoints for the irreversible cancel operation ('Get explicit user confirmation before executing'), but no formal validate->fix->retry feedback loops or checklists are present.	4 / 5
Progressive Disclosure	Sections are well organized, but with no bundle files and ~250 lines entirely inline — including a 17-row Quick Reference table and consolidated pitfalls — reference material that could live in separate files is not progressively disclosed.	3 / 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 and clearly niched to Calendly, but it lacks an explicit 'Use when...' activation clause, which caps its completeness. Adding concrete trigger phrases would lift the weakest dimension.

Suggestions

Append an explicit activation clause such as 'Use when the user wants to schedule, view, or cancel Calendly meetings, check availability, or manage Calendly organization members.'

Include a few more natural synonyms users say ('bookings', 'meetings', 'calendar invites') to broaden trigger coverage.

Keep the third-person voice ('Automate') which already aligns with the rubric's voice guidance.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete action areas — 'scheduling, event management, invitee tracking, availability checks, and organization administration' — giving comprehensive coverage of the Calendly domain rather than vague abstraction.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no explicit 'Use when...' trigger clause; 'Always search tools first for current schemas' is operational instruction, not activation guidance, so per the rubric cap completeness stays at 3.	3 / 5
Trigger Term Quality	Natural user-facing terms like 'Calendly scheduling', 'availability checks', and 'invitee tracking' are present, but a few common variants a user might say (e.g. 'bookings', 'meetings', 'calendar invites') are missing, so it stops short of the comprehensive-synonym bar.	4 / 5
Distinctiveness Conflict Risk	'Calendly' is a highly specific niche and every action is scoped to it via Rube MCP (Composio), giving clear distinct triggers with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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: a9fa86d

Reviewed: about 19 hours 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.