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.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/cal-com-automation/SKILL.md

The canonical home for this skill is cal-com-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a dense, well-structured MCP tool reference with concrete tool slugs, parameters, and validation checkpoints across most workflows. Its main weaknesses are duplicated pitfall content and a vague, circular 'When to Use' section.

Suggestions

Remove the duplicated 'Known Pitfalls' recap or the per-workflow 'Pitfalls' so date-format and event-type guidance appears once, cutting tokens.

Add verify/recovery steps to the team-creation and webhook-delete flows (e.g., re-list after create, confirm deletion) to make validation consistent.

Replace the circular 'When to Use' line with concrete triggers mirroring the description, or delete the section if it adds no signal.

DimensionReasoningScore

Conciseness

Mostly efficient with no concept-explaining fluff, but the 'Known Pitfalls' section duplicates the per-workflow 'Pitfalls' (date formats, event types) and the Quick Reference table re-lists tool slugs/params already given, so it could be tightened.

3 / 5

Actionability

Provides concrete tool slugs and exact parameter names/formats ('CAL_POST_NEW_BOOKING_REQUEST', 'eventTypeId', ISO 8601 with timezone), but the flows are numbered pseudocode rather than fully worked tool-call examples, leaving minor gaps.

4 / 5

Workflow Clarity

Clear numbered sequences with validation checkpoints in the key flows ('Confirm connection status shows ACTIVE', 'Confirm booking creation response', 'Verify webhook fires on test booking'); minor gaps remain where team/webhook-delete flows lack a verify step, so it is below the explicit-feedback-loops anchor at 5.

4 / 5

Progressive Disclosure

Well-organized into clear sections with no nested references and no bundle files to misroute, but as a single ~200-line file the consolidated pitfalls and Quick Reference could split into a reference file, and the trailing 'When to Use' is circular.

4 / 5

Total

15

/

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 distinct, listing four concrete Cal.com actions in a clearly bounded niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to schedule, reschedule, or manage Cal.com bookings, check availability, or configure booking webhooks.'

Include natural synonyms like 'scheduling', 'appointments', and 'calendar' alongside 'bookings' to broaden trigger-term coverage.

Optionally mention '.ics'/calendar-export intent if webhook or booking export flows are common requests.

DimensionReasoningScore

Specificity

Names the domain and lists four concrete actions ('manage bookings, check availability, configure webhooks, and handle teams'), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' clause; per the judging guideline a missing trigger clause caps completeness at 3 even though the capability list is clear.

3 / 5

Trigger Term Quality

Good natural-term coverage ('bookings', 'availability', 'webhooks', 'teams', 'Cal.com') but missing common synonyms users would say ('scheduling', 'appointments', 'calendar'), so it sits below the comprehensive anchor at 5.

4 / 5

Distinctiveness Conflict Risk

Targets a distinct niche (Cal.com automation via Rube MCP/Composio) with specific triggers, giving minimal conflict 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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.