outlook-calendar-automation
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.
74
65%
Does it follow best practices?
Impact
90%
1.16xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/outlook-calendar-automation/SKILL.mdQuality
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 is strong in specificity and distinctiveness, clearly naming the tool ecosystem (Rube MCP/Composio) and listing concrete calendar operations. However, it lacks an explicit 'Use when...' clause which would help Claude know exactly when to select this skill, and it could benefit from more natural user-facing trigger terms like 'schedule a meeting' or 'book time'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to schedule meetings, check calendar availability, send calendar invites, or manage Outlook Calendar events.'
Include more natural user trigger terms such as 'schedule a meeting', 'book time', 'calendar invite', 'reschedule', 'cancel meeting', or 'check availability'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create events, manage attendees, find meeting times, and handle invitations.' Also specifies the tool chain (Rube MCP, Composio) and includes a procedural note about searching tools first. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause. The 'when' is only implied by the action descriptions. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'Outlook Calendar', 'events', 'attendees', 'meeting times', 'invitations', but misses common user variations like 'schedule a meeting', 'book a room', 'calendar invite', '.ics', or 'reschedule'. The technical terms 'Rube MCP' and 'Composio' are not user-facing trigger terms. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of 'Outlook Calendar', 'Rube MCP (Composio)', and calendar-specific actions. Unlikely to conflict with other skills given the narrow, well-defined niche. | 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 is a solid, well-organized reference skill for Outlook Calendar automation with clear workflow sequences and useful pitfall documentation. Its main weaknesses are moderate verbosity (repeated pitfalls, some unnecessary explanations) and the lack of truly executable examples—tool calls are described in numbered steps rather than shown with concrete invocation syntax. The monolithic structure would benefit from splitting detailed parameter references and OData examples into separate files.
Suggestions
Deduplicate pitfalls: the per-workflow pitfalls and the 'Known Pitfalls' section repeat the same information (e.g., attendee replacement, datetime formats). Consolidate into one location.
Add at least one fully concrete tool invocation example showing exact parameter values (e.g., a complete RUBE tool call with all required params filled in) rather than just listing parameter names.
Split the OData filter reference, Known Pitfalls, and detailed parameter documentation into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy—pitfalls are repeated across sections and in the 'Known Pitfalls' summary section. Some parameter descriptions are things Claude would know (e.g., explaining ISO 8601 format). The content could be tightened by ~30% without losing information. | 2 / 3 |
Actionability | Tool sequences are clearly named and parameters are well-documented, but the code examples are pseudocode/numbered-step descriptions rather than actual executable tool calls. The OData filter examples are concrete and useful, but the workflow steps lack copy-paste-ready tool invocation syntax with full parameter examples. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional, Alternative). Each workflow includes explicit ordering, and pitfalls sections serve as validation checkpoints. The Event ID Resolution pattern shows a clear find-then-act sequence. The setup section includes a verification step before proceeding. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's a monolithic ~250-line file with no bundle files to offload detailed content. The OData filter examples, known pitfalls, and detailed parameter lists for each workflow could be split into separate reference files. The external link to Composio docs is helpful but insufficient for progressive disclosure. | 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 | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.