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.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill calendly-automation77
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.
This description effectively communicates specific Calendly-related capabilities and is clearly distinguishable from other skills due to the explicit platform reference. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords like 'meetings', 'appointments', or 'book time' that users commonly say when needing scheduling help.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user mentions Calendly, scheduling meetings, booking appointments, or checking availability'
Include additional natural trigger terms users might say: 'meetings', 'appointments', 'book time', 'schedule a call', 'calendar link'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'scheduling, event management, invitee tracking, availability checks, and organization administration'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with specific capabilities, but lacks an explicit 'Use when...' clause. The instruction to 'search tools first' is implementation guidance, not trigger guidance for when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes 'Calendly' and 'scheduling' which are natural terms, but misses common variations users might say like 'calendar', 'meetings', 'book time', 'appointments', or 'schedule a call'. | 2 / 3 |
Distinctiveness Conflict Risk | The explicit mention of 'Calendly' and 'Rube MCP (Composio)' creates a clear niche. This is unlikely to conflict with generic calendar or scheduling skills due to the specific platform reference. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill for Calendly automation with clear workflow sequences and explicit pitfall documentation. The main weakness is verbosity - pitfalls and URI format warnings are repeated across sections, and the document could benefit from consolidating common patterns and potentially splitting detailed workflows into separate reference files.
Suggestions
Consolidate repeated pitfalls (URI formats, scope requirements) into the 'Common Patterns' section and reference them from workflows instead of repeating
Consider splitting detailed workflow sections into separate files (e.g., WORKFLOWS.md) with SKILL.md serving as a concise overview with links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - pitfalls are repeated across sections, and some explanations (like URI format reminders) appear multiple times. The content could be tightened by consolidating common patterns earlier and reducing repetition. | 2 / 3 |
Actionability | Provides concrete tool sequences with specific parameter names, exact URI formats, and clear examples. The quick reference table and explicit parameter listings make this highly actionable and copy-paste ready for Claude to execute. | 3 / 3 |
Workflow Clarity | Each workflow has clear numbered sequences with explicit prerequisite/required/optional labels. The Cancel Events workflow appropriately includes confirmation steps before destructive action. Tool sequences are well-ordered with validation checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but it's a monolithic document that could benefit from splitting detailed workflows into separate files. The quick reference table at the end is helpful, but the 200+ lines of inline content could be better organized with external references. | 2 / 3 |
Total | 10 / 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.