Name: microsoft-outlook
Rating: 55.2 (1 reviews)
Author: membranedev

microsoft-outlook

Microsoft Outlook integration. Manage communication data, records, and workflows. Use when the user wants to interact with Microsoft Outlook data.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/microsoft-outlook/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 highly actionable with executable Membrane CLI commands and a clear state-driven connection workflow. Its main weakness is conciseness: an unnecessary Outlook-explainer intro and some padding could be trimmed, and the invocation style is inconsistent.

Suggestions

Remove or condense the opening paragraph that defines Outlook and its user base; Claude already knows this and it adds tokens without guidance.

Standardize on one invocation form (either `membrane` or `npx @membranehq/cli@latest`) throughout, and de-duplicate the `action list` command that appears in both 'Searching for actions' and 'Popular actions'.

Label the post-connection workflow explicitly as 'Step 2' (or restructure into numbered steps) so the 'skip to Step 2' references resolve.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Outlook is and who uses it ('Microsoft Outlook is a Microsoft-developed email and calendaring application... Many businesses rely on Outlook...') which Claude already knows, plus minor prose padding, matching anchor 3 rather than 4.	3 / 5
Actionability	It provides copy-paste executable commands for install, login, connection, action list/run, and proxy requests with a flags table, but the npx-vs-membrane invocation inconsistency and a duplicated action-list command are minor gaps, matching anchor 4 rather than 5.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-driven checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but 'skip to Step 2' references an unlabeled step, matching anchor 4 rather than 5.	4 / 5
Progressive Disclosure	The single-file body is organized into clear sections (install, auth, connecting, searching, running, proxy, best practices), but no bundle files or external references are signaled and some inlineable bulk (proxy flags, clientAction spec) could be split out, matching anchor 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly identifies the Outlook niche and includes an explicit 'Use when' trigger, but its action language and trigger keywords are generic. Adding concrete capabilities (email, calendar, contacts) and the natural terms users say would lift specificity and trigger quality.

Suggestions

Replace 'Manage communication data, records, and workflows' with concrete actions such as 'Send and read email, manage calendar events, contacts, and tasks'.

Expand the trigger to name what users actually say, e.g. 'Use when the user wants to send or read Outlook email, manage their calendar, or work with contacts and tasks.'

Drop the filler word 'integration' from the opening and lead with the concrete capabilities to increase specificity.

Dimension	Reasoning	Score
Specificity	It names the domain ('Microsoft Outlook integration') but the only actions are generic ('Manage communication data, records, and workflows') with no concrete verbs like send email or create events, matching anchor 2 rather than 3.	2 / 5
Completeness	Both 'what' (manage communication data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Microsoft Outlook data') are present, but both are generic, matching anchor 4 rather than 5.	4 / 5
Trigger Term Quality	It includes relevant keywords ('Microsoft Outlook', 'interact with Microsoft Outlook data') but omits the natural terms users actually say (email, calendar, contacts), matching anchor 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app ('Microsoft Outlook integration') gives it a clear niche with minimal conflict risk, though there is minor overlap with generic email/communication skills, matching anchor 4.	4 / 5
	Total	13 / 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: membranedev/application-skills
Path: skills/microsoft-outlook/SKILL.md
Commit: f484c82

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.