CtrlK
BlogDocsLog inGet started
Tessl Logo

outlook-automation

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

77

1.53x
Quality

67%

Does it follow best practices?

Impact

97%

1.53x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

72%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 a well-structured, operational reference with concrete tooling guidance and clean navigation; its main weakness is the absence of validation feedback loops in the destructive creation workflows.

Suggestions

Add a verify step to the create workflows (e.g., after OUTLOOK_CREATE_CONTACT, confirm the contact appears via OUTLOOK_LIST_CONTACTS or by reading the returned id).

Collapse the standalone 'Known Pitfalls' section into the per-workflow pitfalls or keep only items not already covered to reduce redundancy.

Optionally include one minimal example tool-call payload shape to anchor the dynamic-schema guidance.

DimensionReasoningScore

Conciseness

Lean and operational throughout (tool sequences, key parameters, pitfalls), assuming Claude's knowledge of Outlook/KQL/OData; minor redundancy between the per-section 'Pitfalls' and the recap 'Known Pitfalls' section could be trimmed.

4 / 5

Actionability

Concrete tool slugs, exact parameter names and value examples, and ready-to-use KQL/OData snippets give mostly executable guidance; full sample call payloads are intentionally deferred to dynamic schemas.

4 / 5

Workflow Clarity

Tool sequences are clearly tagged [Required]/[Optional]/[Prerequisite] and the Setup section has validation checkpoints, but destructive/batch workflows (create contact, create folder) lack verify-after-creation feedback loops, capping workflow clarity at 3.

3 / 5

Progressive Disclosure

A single, well-organized SKILL.md with clear section hierarchy and one external doc link; with no bundle files needed, the well-structured overview earns a full score.

5 / 5

Total

16

/

20

Passed

Description

62%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 clearly scopes a niche capability with concrete feature areas, but lacks an explicit 'when to use' trigger clause and leans slightly technical, capping completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when the user wants to send, search, or organize Outlook emails, schedule calendar events, or manage contacts').

Soften the technical framing by leading with user-facing terms before 'via Rube MCP (Composio)'.

Include common synonyms a user might say (e.g., 'meetings', 'inbox', 'mail') to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ('emails, calendar, contacts, folders, attachments') tied to a named automation mechanism, with only minor gaps in coverage.

4 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause; the closing instruction ('Always search tools first') is procedural rather than an invocation trigger, which caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms ('emails', 'calendar', 'contacts', 'Outlook') but leans on technical framing ('Rube MCP (Composio)') and omits common synonyms a user would naturally say.

3 / 5

Distinctiveness Conflict Risk

A clear niche (Microsoft Outlook automation via Rube MCP/Composio) with distinct triggers and minimal conflict risk against other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.