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.

59

Quality

69%

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-claude/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

68%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 content is well-structured and actionable, with concrete MCP tool slugs and parameters across five workflows, but destructive operations lack validation checkpoints and some sections are padded or redundant. Tightening validation and de-duplicating pitfalls would lift the weaker dimensions.

Suggestions

Add explicit validation/confirm steps to destructive workflows, e.g. before CAL_DELETE_WEBHOOK_BY_ID require listing and confirming the target webhook, and after booking creation verify the returned booking ID and status.

Remove the redundant 'Known Pitfalls' section or fold its unique items into the per-workflow Pitfalls blocks to eliminate duplication.

Replace the empty 'When to Use' filler with concrete trigger guidance or delete it, since it adds tokens without information.

DimensionReasoningScore

Conciseness

The body is mostly lean with tables, tool sequences, and bulleted pitfalls, though the closing 'When to Use' filler and the duplicated 'Known Pitfalls' section add minor padding that could be trimmed.

4 / 5

Actionability

Concrete tool slugs (e.g. CAL_FETCH_ALL_BOOKINGS, CAL_POST_NEW_BOOKING_REQUEST) with typed key parameters and format examples give executable guidance, though no full sample invocations with argument values are shown.

4 / 5

Workflow Clarity

Workflows are clearly sequenced with some checkpoints (confirm ACTIVE connection, verify webhook fires), but destructive operations like CAL_DELETE_WEBHOOK_BY_ID and batch booking flows lack explicit validation steps, capping this at 3 per the rubric.

3 / 5

Progressive Disclosure

A single well-organized SKILL.md with clear section headers and no external bundle files; minor redundancy between per-workflow pitfalls and the 'Known Pitfalls' section keeps it just below the ideal.

4 / 5

Total

15

/

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.

The description is specific and clearly distinct, naming four concrete Cal.com operations, but it omits explicit 'when to use' trigger guidance, which caps its completeness. Adding a 'Use when...' clause would raise the strongest-scoring weakness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to manage Cal.com bookings, check availability, set up webhooks, or administer teams.'

Include common synonyms users say naturally, such as 'scheduling', 'calendar', or 'meetings', to broaden trigger coverage.

Drop or relocate 'Always search tools first for current schemas' (operational guidance) out of the description to keep it focused on capability and triggers.

DimensionReasoningScore

Specificity

Lists several concrete actions ('manage bookings, check availability, configure webhooks, and handle teams') within the Cal.com domain, but does not enumerate each operation's sub-actions, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

The description clearly states what the skill does but lacks any 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural keywords like 'bookings', 'availability', 'webhooks', and 'teams' align with what a user would say, though synonyms like 'scheduling', 'calendar', or 'meetings' are missing.

4 / 5

Distinctiveness Conflict Risk

The Cal.com-via-Rube-MCP niche is specific and well-scoped, with distinct triggers unlikely to overlap with unrelated skills.

5 / 5

Total

16

/

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.