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.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill cal-com-automation71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 effectively communicates specific capabilities for Cal.com automation with good distinctiveness due to platform-specific naming. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords like 'scheduling' or 'appointments' that users would actually say.
Suggestions
Add a 'Use when...' clause with trigger terms like 'when the user mentions Cal.com, scheduling meetings, booking appointments, or checking calendar availability'
Include common synonyms users might say: 'calendar', 'scheduling', 'appointments', 'meeting slots', 'book a time'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'manage bookings, check availability, configure webhooks, and handle teams.' These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (manage bookings, check availability, etc.) but lacks an explicit 'Use when...' clause. The instruction to 'search tools first' is operational guidance, not trigger guidance. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Cal.com', 'bookings', 'availability', 'webhooks', and 'teams', but missing common variations users might say like 'calendar', 'scheduling', 'appointments', 'meeting slots'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche with 'Cal.com' and 'Rube MCP (Composio)' as distinct identifiers. Unlikely to conflict with other calendar or scheduling skills due to the specific platform mention. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive coverage of Cal.com operations with clear workflow sequences and good organization. However, it lacks executable code examples (only pseudocode patterns), has some redundancy in pitfall documentation, and could be more concise by consolidating repeated information and splitting into multiple files.
Suggestions
Add executable code examples showing actual tool calls with sample parameters and expected response structures, not just pseudocode steps
Consolidate the repeated date/time format pitfalls into a single 'Date/Time Reference' section instead of repeating in each workflow
Consider splitting detailed workflow sections (webhooks, teams) into separate reference files, keeping SKILL.md as a concise overview with the quick reference table
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - pitfalls are repeated across sections, and some explanations (like date format examples appearing multiple times) could be consolidated. The quick reference table at the end duplicates information already covered in workflows. | 2 / 3 |
Actionability | Provides tool names and parameter lists, but lacks executable code examples. The 'Common Patterns' section uses pseudocode-style numbered steps rather than actual API calls or code snippets. No concrete input/output examples showing actual payloads. | 2 / 3 |
Workflow Clarity | Clear multi-step sequences with explicit tool ordering marked as [Required] or [Optional]. The Booking Creation Flow shows a proper validation pattern (check availability before booking). Setup section has clear sequential steps with verification. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one file. The document is quite long (~200 lines) and could benefit from splitting detailed workflow sections or the pitfalls into separate reference files. Only external link is to Composio docs. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.