CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webiny-configure-entraid

Configuring Microsoft Entra ID (formerly Azure AD) as a federated identity provider for Webiny projects using Cognito Federation. Use this skill when the developer asks about Entra ID, Azure AD, Microsoft SSO, OIDC with Microsoft, Microsoft login for Webiny, or configuring login.microsoftonline.com as an identity provider. Also relevant for tenant IDs, Entra application registration, or connecting Microsoft 365 accounts to Webiny.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

Highly actionable content with concrete code, commands, and a clear deploy workflow, but it suffers from repeated boilerplate across examples and a monolithic structure with no progressive disclosure into reference files.

Suggestions

Factor the repeated providerDetails block into a single canonical example and have later examples show only the differing fields (e.g., allowCredentialsLogin, logoutUrls, attributeMapping, mfa) to reduce token cost.

Move the six full examples and/or the reference tables into a references/ file (e.g., EXAMPLES.md) and link to it from SKILL.md, keeping only the quick-start and deploy order inline.

Add an explicit post-deploy validation step (e.g., confirm the "Sign in with Microsoft" button appears and a test login completes) to close the workflow's verification gap.

DimensionReasoningScore

Conciseness

The skill is mostly efficient and domain-specific, but the identical providerDetails block (attributes_request_method, authorize_scopes, client_id/secret/issuer) is repeated verbatim across Examples 1, 2, 4, 5, and 6 — padding that could be factored out.

3 / 5

Actionability

Fully executable, copy-paste-ready TSX extensions, concrete environment variables, exact deploy commands ("yarn webiny deploy core --env=dev"), file paths, and a deploy-order checklist covering the common cases.

5 / 5

Workflow Clarity

Clear numbered deploy sequence with the redirect-URI feedback loop (deploy core → read cognitoUserPoolDomain output → update Entra redirect URI → deploy api/admin), but no explicit post-deploy validation that the federation actually works.

4 / 5

Progressive Disclosure

Well-organized into sections (TL;DR, Prerequisites, Reference Tables, Full Examples, Quick Reference), but it is a ~360-line monolith with no bundle files or one-level-deep references, and the six full examples plus reference tables are candidates for separate files.

3 / 5

Total

15

/

20

Passed

Description

90%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.

A strong, well-scoped description that clearly states what the skill does and when to use it, with rich, natural trigger terms and a distinct Microsoft-for-Webiny niche. The only mild gap is specificity, which names a single configuring action rather than enumerating several.

DimensionReasoningScore

Specificity

Names the domain and one concrete action — "Configuring Microsoft Entra ID (formerly Azure AD) as a federated identity provider for Webiny projects using Cognito Federation" — but does not enumerate multiple distinct actions, matching the anchor for naming a domain with 1-2 concrete actions.

3 / 5

Completeness

Explicitly answers both what ("Configuring Microsoft Entra ID… as a federated identity provider… using Cognito Federation") and when ("Use this skill when the developer asks about…") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms and specifics: "Entra ID, Azure AD, Microsoft SSO, OIDC with Microsoft, Microsoft login for Webiny, …login.microsoftonline.com… tenant IDs, Entra application registration, … Microsoft 365 accounts" — these are exactly the phrases a developer would say.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Webiny + Microsoft Entra ID via Cognito Federation) with Microsoft-specific triggers that would not fire for the Okta/Auth0 alternatives, giving minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

webiny/webiny-js

Path

skills/user-skills/configure-entraid/SKILL.md

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.