Name: microsoft-graph-api
Rating: 60.8 (1 reviews)
Author: membranedev

microsoft-graph-api

Microsoft Graph API integration. Manage data, records, and automate workflows. Use when the user wants to interact with Microsoft Graph API data.

Quality

71%

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-graph-api/SKILL.md

Quality

Content

81%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 concrete, executable Membrane CLI commands and a clearly sequenced connection workflow. Its main gaps are a small amount of concept-explanation padding at the top and a few inconsistent/broken step cross-references plus no validation step after action/proxy execution.

Suggestions

Trim or remove the opening 'The Microsoft Graph API is a RESTful web API...' paragraph — Claude already knows what Graph is.

Fix the 'skip to Step 2' references by actually numbering the steps (Step 1 connect, Step 2 search actions, Step 3 run) so navigation is unambiguous.

Add a validation/verification checkpoint after running actions or proxy requests (e.g. check the `output`/error field and handle non-2xx or `CLIENT_ACTION_REQUIRED` before proceeding).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, actionable CLI commands with light context; the main over-explanation is the opening 'The Microsoft Graph API is a RESTful web API...' paragraph and the 'focus on the integration logic rather than auth plumbing' aside, both of which Claude already knows.	4 / 5
Actionability	Nearly every section gives copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request proxy) with concrete flags and JSON-output examples covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state handling and a poll-after-action loop, but the section labels are inconsistent ('skip to Step 2' with no numbered Step 2) and there is no validation checkpoint after running an action or proxy request.	4 / 5
Progressive Disclosure	The SKILL.md is a single-file overview with clear section headers and no nested references, which is appropriate for a skill with no bundle files; the inlined clientAction schema and proxy flag table could arguably live in a reference file, hence not a 5.	4 / 5
	Total	17 / 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 is clear and distinct, naming the domain and including an explicit 'Use when' trigger. Its weaknesses are vague, generic verbs ('Manage data, records, and automate workflows') and a narrow trigger that omits the natural Microsoft-ecosystem terms users say.

Suggestions

Replace abstract verbs with concrete Graph capabilities, e.g. 'Read and send Outlook mail, manage calendar events, access OneDrive files, and query Azure AD users.'

Broaden the trigger to the terms users actually say: 'Use when the user wants to work with Microsoft Graph, Outlook, OneDrive, Azure AD, or Microsoft 365 data.'

Drop 'records' and 'automate workflows' — they are generic filler that adds no Microsoft Graph specificity.

Dimension	Reasoning	Score
Specificity	It names the domain and a few generic actions ("Manage data, records, and automate workflows") but the actions are abstract — no concrete Microsoft Graph operations like reading mail, calendar events, or files are listed.	3 / 5
Completeness	It has a clear what ("Microsoft Graph API integration. Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Microsoft Graph API data"), though the when trigger is fairly narrow and single-phrased.	4 / 5
Trigger Term Quality	"Microsoft Graph API" is the main natural keyword and it is repeated, but synonyms users actually say (Outlook, OneDrive, Azure AD, M365, emails, calendar) are absent from the description.	3 / 5
Distinctiveness Conflict Risk	Microsoft Graph API is a distinct niche with a clear trigger unlikely to collide with unrelated skills, with only minor overlap risk against generic API-integration skills.	4 / 5
	Total	14 / 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-graph-api/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.