CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

Install with Tessl CLI

npx tessl i github:Lingjie-chen/MT5 --skill outlook-calendar-automation
What are skills?

77

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

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 Outlook Calendar automation with good distinctiveness through platform-specific naming. However, it lacks an explicit 'Use when...' clause and could benefit from additional natural trigger terms that users commonly say when requesting calendar help.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to schedule meetings, check availability, send calendar invites, or manage Outlook appointments'

Include additional natural trigger terms users would say: 'schedule', 'appointment', 'book a meeting', 'availability', 'calendar invite'

DimensionReasoningScore

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' (create events, manage attendees, etc.) but lacks an explicit 'Use when...' clause. The 'when' is only implied through the capability list, not explicitly stated.

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 'availability'.

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

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 Outlook Calendar automation with clear workflow sequences and comprehensive pitfall documentation. The main weakness is verbosity - the skill could be more concise by consolidating repeated concepts and potentially splitting detailed reference material into separate files. The actionability and workflow clarity are excellent with specific tool names, parameters, and validation checkpoints.

Suggestions

Consolidate timezone handling and datetime format guidance into a single 'DateTime Reference' section instead of repeating across workflows and pitfalls

Consider moving the detailed OData filter syntax examples and Known Pitfalls to a separate REFERENCE.md file, keeping only essential warnings inline

Remove the Quick Reference table as it largely duplicates information already present in the workflow sections

DimensionReasoningScore

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 concrete tool sequences, specific parameter names with exact values, OData filter syntax examples, and clear patterns like ISO 8601 datetime formats. The guidance is copy-paste ready with specific tool slugs and parameter structures.

3 / 3

Workflow Clarity

Each workflow has clear numbered sequences with [Required], [Optional], and [Prerequisite] markers. Includes explicit validation steps like 'Confirm connection status shows ACTIVE before running any workflows' and error handling guidance for 400 errors.

3 / 3

Progressive Disclosure

Content is well-organized with clear sections, but everything is in a single monolithic file. The extensive pitfalls, patterns, and reference sections could be split into separate files. The external link to Composio docs is good but internal structure could benefit from splitting.

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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.