outlook-automation

Automate Outlook tasks via Rube MCP (Composio): emails, calendar, contacts, folders, attachments. Always search tools first for current schemas.

1.53x

Quality

72%

Does it follow best practices?

Impact

97%

1.53x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/outlook-automation/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and highly actionable for an MCP-tooling skill, with clear workflow sequences and concrete parameters throughout. Its main weaknesses are redundant content (duplicated pitfalls section, overlapping quick-reference table) and a lack of complete example invocations or per-workflow validation steps.

Suggestions

Merge the "Known Pitfalls" section into the relevant workflows (or keep only the summary table) to eliminate the duplicated account-type and field-confusion entries.

Add one or two complete example tool invocations (e.g., a full OUTLOOK_SEARCH_MESSAGES call with query, from_index, size) to make guidance copy-paste ready.

Add brief verification steps within workflows (e.g., confirm a non-empty result set before paginating, verify folder ID resolution before querying) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense and efficient (tool sequences, parameters, pitfalls), but the "Known Pitfalls" section repeats the account-type and field-confusion pitfalls already stated in workflows 1 and 3, and the Quick Reference table re-lists tools already covered — content that could be tightened.	3 / 5
Actionability	For an instruction-only MCP skill, guidance is concrete and mostly executable: exact tool slugs (OUTLOOK_SEARCH_MESSAGES), parameter names, and copy-paste-ready KQL/OData snippets ("from:user@example.com", "isRead eq false"); the gap is the absence of complete example invocations showing a full tool call.	4 / 5
Workflow Clarity	Each of the five workflows has a "When to use" statement, a sequenced tool list marked Required/Optional, and the Setup section includes explicit verification checkpoints ("Confirm connection status shows ACTIVE before running any workflows"); minor validation gaps remain within individual workflows.	4 / 5
Progressive Disclosure	No bundle files exist, so the skill is appropriately self-contained: clear section headers, a compact navigable quick-reference table, and a single well-signaled outbound link. Structure is good with only minor organization gains possible (e.g., splitting the KQL/OData syntax reference).	4 / 5
	Total	15 / 20 Passed

Description

66%Weight 40%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 is concise, specific about capability areas, and clearly distinct, but it lacks any explicit "when to use" trigger guidance, which limits its completeness. Adding a use-when clause and natural synonyms would raise it to the top band.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Outlook, Microsoft 365 mail, calendar events, or asks to search/send/organize emails and contacts."

Include common synonyms users naturally say ("meetings", "events", "invites", "mail") alongside the current noun list.

Replace the generic verb "Automate Outlook tasks" with 1-2 concrete actions (e.g. "Search and send emails, create calendar events, manage contacts").

Dimension	Reasoning	Score
Specificity	Enumerates several concrete capability areas ("emails, calendar, contacts, folders, attachments") within a named domain, but relies on a single generic verb ("Automate Outlook tasks") rather than naming specific actions, leaving minor gaps versus the fully comprehensive anchor.	4 / 5
Completeness	The "what" is clearly stated (automating Outlook emails, calendar, contacts, folders, attachments), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Includes natural terms users would say ("Outlook", "emails", "calendar", "contacts", "attachments") plus the technical trigger "Rube MCP (Composio)" for tool-specific queries, but misses common synonyms like "meetings", "events", "invites", or "mail".	4 / 5
Distinctiveness Conflict Risk	"Outlook" plus "Rube MCP (Composio)" carves a clear niche that is unlikely to trigger for unrelated skills; only minor overlap risk with other email/calendar provider skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/outlook-automation/SKILL.md
Commit: 10bfc43

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.