Automate Outlook Calendar tasks via Rube MCP (Composio): create events, manage attendees, find meeting times, and handle invitations. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill outlook-calendar-automation74
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/skillEvaluation — 90%
↑ 1.16xAgent success when using this skill
Validation 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 capabilities for Outlook Calendar automation with good technical context (Rube MCP/Composio). However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms that users would actually say when requesting calendar help.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to schedule meetings, book appointments, check availability, or manage Outlook calendar events.'
Include additional natural trigger terms users might say: 'schedule', 'appointment', 'book a meeting', 'free time', 'availability', 'calendar invite'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create events, manage attendees, find meeting times, and handle invitations' - these are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (automate Outlook Calendar tasks with specific actions), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the capability description. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Outlook Calendar', 'events', 'attendees', 'meeting times', 'invitations', but missing common variations users might say like 'schedule', 'appointment', 'book a meeting', 'calendar invite', or '.ics'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to 'Outlook Calendar' and 'Rube MCP (Composio)' - this specific platform and tooling combination creates a distinct niche unlikely to conflict with generic calendar or scheduling skills. | 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 Outlook Calendar operations with excellent workflow clarity and explicit tool sequences. However, it lacks executable code examples (showing only parameter names rather than complete invocations) and could be more concise by eliminating redundant explanations of datetime/timezone handling across multiple sections.
Suggestions
Add complete, executable tool invocation examples showing actual JSON/parameter structures for at least the Create Event and List Events workflows
Consolidate datetime/timezone handling guidance into a single section and reference it from workflows instead of repeating across multiple sections
Consider splitting Known Pitfalls and OData Filter Syntax into a separate REFERENCE.md file to reduce main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., repeating timezone handling concepts across multiple sections, explaining OData syntax multiple times). 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 shows filter syntax as strings but not complete tool invocations. Pseudocode-style numbered steps rather than copy-paste ready examples. | 2 / 3 |
Workflow Clarity | Excellent workflow structure with clear tool sequences, explicit [Required]/[Optional]/[Prerequisite] markers, and comprehensive pitfalls sections. Each workflow has logical steps with validation checkpoints (e.g., verify connection ACTIVE before proceeding). | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one monolithic file. The extensive Known Pitfalls and Common Patterns sections could be split into separate reference files. No external file references for advanced topics. | 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 | |
Table of Contents
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.