setup-auth
This skill should be used when the user asks to "set up authentication", "add login", "add logout", "configure Entra ID", "set up Azure AD auth", "add Microsoft login", "enable authentication", "set up sign in", "add role-based access", "add authorization", "protect routes", "add auth to my site", "configure identity provider", or wants to set up authentication (login/logout via Microsoft Entra ID) and role-based authorization for their Power Pages code site.
Install with Tessl CLI
npx tessl i github:microsoft/power-platform-skills --skill setup-auth87
Quality
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger term coverage and completeness with explicit 'when to use' guidance, and is highly distinctive due to its specific technology focus (Microsoft Entra ID + Power Pages). The main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond just 'authentication and role-based authorization'.
Suggestions
Add specific concrete actions like 'configures app registration', 'sets up redirect URIs', 'implements role claims mapping', or 'creates authentication middleware' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'authentication (login/logout via Microsoft Entra ID) and role-based authorization for Power Pages code site' which names the domain and some actions, but doesn't list comprehensive concrete actions like 'configure identity provider settings', 'set up redirect URIs', or 'implement token validation'. | 2 / 3 |
Completeness | The description explicitly answers both 'what' (authentication/authorization for Power Pages via Microsoft Entra ID) and 'when' with an extensive list of trigger phrases prefaced by 'This skill should be used when the user asks to...'. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including variations like 'set up authentication', 'add login', 'configure Entra ID', 'set up Azure AD auth', 'add Microsoft login', 'protect routes', 'add auth to my site' - these are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (Microsoft Entra ID, Azure AD, Power Pages) that clearly differentiates it from generic auth skills or other identity provider integrations. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent workflow clarity and progressive disclosure. The eight-phase approach with explicit checkpoints, decision points, and verification steps demonstrates strong process design. Minor verbosity in phase descriptions and some redundancy between the workflow overview and phase details prevent a perfect conciseness score.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeating framework patterns across phases, verbose phase descriptions). Some sections could be tightened—the workflow overview duplicates information found in phase details. | 2 / 3 |
Actionability | Provides concrete, executable guidance throughout: specific file paths, actual code snippets, exact PowerShell commands, and clear function signatures. The auth service implementation details and framework-specific patterns are copy-paste ready. | 3 / 3 |
Workflow Clarity | Excellent multi-phase workflow with explicit validation checkpoints (Phase 7 verification), clear decision points documented in a summary table, and feedback loops (e.g., 'If build fails, fix before proceeding'). Each phase has clear goals, actions, and outputs. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, phased approach, and appropriate references to external files (framework-conventions.md, authentication-reference.md, authorization-reference.md). Content is organized into digestible phases with clear navigation via the workflow summary. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (587 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.