Name: microsoft-entra-id
Rating: 64.8 (1 reviews)
Author: membranedev

microsoft-entra-id

Microsoft Entra ID integration. Manage Users, Applications, ServicePrincipals, Devices, RoleDefinitions, Policies and more. Use when the user wants to interact with Microsoft Entra ID data.

Quality

77%

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-entra-id/SKILL.md

Quality

Content

76%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 content is highly actionable with concrete Membrane CLI commands and a clear connection workflow, held back by a missing validation step around destructive action execution and some introductory over-explanation. Structure is solid though slightly reference-heavy inline.

Suggestions

Add a verification step after destructive/batch actions (e.g., re-run a list action or check the response state field) to create a validate-then-confirm feedback loop.

Trim the introductory paragraph explaining what Microsoft Entra ID is, since Claude already knows this; lead with the Membrane CLI workflow instead.

Consider moving the popular-actions table and proxy flag reference into a separate reference file linked from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven, but the opening paragraph ("Microsoft Entra ID (formerly Azure AD) is a cloud-based identity and access management service...") and the "so you can focus on the integration logic rather than auth plumbing" sentence explain concepts Claude already knows and could be trimmed.	4 / 5
Actionability	Concrete, copy-paste-ready commands cover the full flow (install, login, connection ensure, poll, action list/run, request proxy) and a popular-actions table with keys, fully executable for the common cases.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with state-based polling and feedback loops, but the "Running actions" section executes destructive operations (delete-user, delete-group) with no validation or verification of the result, capping this dimension at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references, but the sizable inline popular-actions table and proxy-options table are reference material that could live in a separate file, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

78%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 specific and clearly scoped to Microsoft Entra ID with an explicit use-when trigger, scoring well on distinctiveness and completeness. It could improve by adding action-verb variety and natural synonyms like "Azure AD."

Suggestions

Vary the action verbs beyond "Manage" (e.g., create, update, list, delete users/groups/applications) to make capabilities more concrete.

Add natural synonyms such as "Azure AD" or "Azure Active Directory" to the trigger clause so it fires on common user phrasings.

Expand the "Use when..." clause with concrete trigger variations (e.g., "or when the user mentions Entra ID users, groups, or service principals").

Dimension	Reasoning	Score
Specificity	"Manage Users, Applications, ServicePrincipals, Devices, RoleDefinitions, Policies and more" lists several specific resource types, but the single verb "Manage"/"interact" leaves minor gaps in the concrete-action vocabulary that a 5 would enumerate.	4 / 5
Completeness	It answers both what ("Manage Users, Applications...") and when ("Use when the user wants to interact with Microsoft Entra ID data"), but the trigger is a single phrase rather than the varied concrete triggers that define a 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Microsoft Entra ID data" provides good keyword coverage around the product name, but misses natural synonyms a user might say such as "Azure AD" or "Azure Active Directory".	4 / 5
Distinctiveness Conflict Risk	"Microsoft Entra ID integration" carves out a clear niche tied to a specific product, making it highly distinguishable with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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-entra-id/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.