outlook-automation
Automate Outlook tasks via Rube MCP (Composio): emails, calendar, contacts, folders, attachments. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill outlook-automation63
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
32%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 identifies the domain (Outlook via Rube MCP) and lists capability categories but lacks specificity in concrete actions and critically omits explicit trigger guidance. The instruction to 'search tools first' is operational guidance rather than selection criteria, which doesn't help Claude decide when to use this skill.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Outlook, Microsoft email, scheduling meetings in Outlook, or managing Outlook contacts'
Replace category nouns with specific actions: 'send and read emails, schedule meetings, manage contacts, organize folders, download attachments'
Include common user phrasings like 'check my inbox', 'schedule a meeting', 'Outlook calendar', or 'Microsoft 365 email'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Outlook) and lists categories of actions (emails, calendar, contacts, folders, attachments) but doesn't specify concrete actions like 'send emails', 'schedule meetings', or 'download attachments'. | 2 / 3 |
Completeness | Describes what it does (automate Outlook tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Outlook', 'emails', 'calendar', 'contacts', 'attachments' that users might say, but misses common variations like 'meeting invites', 'schedule', 'inbox', or 'Microsoft Outlook'. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Outlook' and 'Rube MCP (Composio)' provides some distinctiveness, but 'emails' and 'calendar' are generic enough to potentially conflict with other email or calendar skills. | 2 / 3 |
Total | 7 / 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, actionable skill with clear workflow sequences and specific tool guidance. The main weaknesses are moderate verbosity with some repeated information across sections, and the monolithic structure that could benefit from splitting into overview + detailed reference files. The pitfalls sections add significant value for avoiding common errors.
Suggestions
Consider moving the Quick Reference table and detailed workflow sections to separate reference files, keeping SKILL.md as a concise overview with links
Consolidate repeated pitfalls (e.g., account type limitations, field confusion) into a single 'Common Pitfalls' section to reduce redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some redundancy (e.g., 'Pitfalls' sections repeat similar warnings across workflows, the Quick Reference table duplicates information already covered). The content is mostly lean but could be tightened. | 2 / 3 |
Actionability | Provides concrete tool names, specific parameter names, exact KQL and OData syntax examples, and clear tool sequences. The guidance is specific and directly usable without pseudocode. | 3 / 3 |
Workflow Clarity | Each workflow has clear numbered sequences with [Required]/[Optional] markers, explicit tool ordering, and detailed pitfalls that serve as validation guidance. The Setup section includes explicit verification steps before proceeding. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~200 lines) that could benefit from splitting detailed workflows or the Quick Reference into separate files. The external toolkit docs link is good but internal structure could be improved. | 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.