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.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/outlook-calendar-automation/SKILL.md

The canonical home for this skill is outlook-calendar-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%Scale 1-5

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, information-rich skill that provides genuinely useful domain-specific knowledge about Outlook Calendar API quirks (OData filter syntax, timezone handling, attendee replacement behavior). Its main weaknesses are redundancy between per-workflow pitfalls and the consolidated 'Known Pitfalls' section, and the monolithic structure that could benefit from splitting reference material into separate files. The actionability is good but would benefit from complete executable tool call examples rather than parameter listings.

Suggestions

Consolidate pitfalls into either per-workflow sections OR the 'Known Pitfalls' section to eliminate redundancy and reduce token count by ~25%.

Split OData filter syntax, timezone handling, and the quick reference table into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with links.

Add at least one complete, executable MCP tool call example (with full parameter object) for the most common workflow (create event) to improve actionability.

Remove the vacuous 'When to Use' section at the bottom — it adds no information beyond the description.

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some redundancy — pitfalls are repeated across sections and the 'Known Pitfalls' section largely restates what was already covered in per-workflow pitfall sections. The 'When to Use' footer is vacuous. Some parameter descriptions are useful domain knowledge Claude wouldn't have, but the overall document could be tightened by ~30%.

3 / 5

Actionability

Provides concrete tool names, parameter names with specific formats, OData filter syntax examples, and clear tool sequences. However, the code blocks are pseudocode/numbered steps rather than executable code, and there are no complete copy-paste examples showing actual MCP tool calls with full parameter objects. The OData filter examples are concrete and useful.

4 / 5

Workflow Clarity

Each workflow has a clear numbered tool sequence with prerequisite/required/optional labels, which is excellent. However, validation/verification steps are mostly implicit — there's no explicit 'verify the event was created successfully' or error-handling feedback loop. The setup section does include a connection verification step. For non-destructive operations this is adequate, but the delete workflow lacks a confirmation checkpoint.

4 / 5

Progressive Disclosure

The content is entirely monolithic in a single file with no bundle files. At ~200+ lines covering 5 distinct workflows plus common patterns, pitfalls, and a quick reference table, some content (like the detailed OData filter syntax, timezone handling, and known pitfalls) could be split into separate reference files. The internal structure with headers is decent but the document is long for a single SKILL.md.

3 / 5

Total

14

/

20

Passed

Description

70%Scale 1-5

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 does a good job specifying concrete calendar management actions and is highly distinctive due to the Outlook Calendar and Rube MCP references. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are solid but could benefit from common synonyms like 'schedule' or 'appointment'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to schedule meetings, create calendar events, manage Outlook appointments, or find available meeting times.'

Include common synonyms and natural phrases users might say, such as 'schedule', 'appointment', 'booking', 'calendar invite', or 'recurring meeting'.

DimensionReasoningScore

Specificity

Lists several specific actions: 'create events, manage attendees, find meeting times, and handle invitations.' These are concrete actions, though coverage could be slightly more comprehensive (e.g., delete events, update events, check availability).

4 / 5

Completeness

The 'what' is clearly stated with specific actions. However, there is no explicit 'Use when...' clause or equivalent trigger guidance. The instruction 'Always search tools first for current schemas' is an implementation note, not a 'when' clause. Per rubric guidelines, missing 'Use when' caps completeness at 3.

3 / 5

Trigger Term Quality

Includes good natural keywords like 'Outlook Calendar', 'events', 'attendees', 'meeting times', 'invitations'. Missing some natural synonyms users might say like 'schedule', 'appointment', 'booking', 'calendar invite', or 'recurring meeting'.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive with specific references to 'Outlook Calendar', 'Rube MCP (Composio)', and calendar-specific actions. This creates a clear niche that is unlikely to conflict with other skills.

5 / 5

Total

16

/

20

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

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.