auth0-aspnetcore-authentication
Use when adding login, logout, and user profile to an ASP.NET Core MVC, Razor Pages, or Blazor Server web application using cookie-based authentication - integrates Auth0.AspNetCore.Authentication for server-rendered apps with login/callback/profile/logout flows.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 is an excellent skill description that clearly communicates both what the skill does and when to use it. It leads with a 'Use when' clause containing specific trigger scenarios, names concrete technologies and authentication flows, and is distinctive enough to avoid conflicts with other skills. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'adding login, logout, and user profile' and specifies the technology stack (ASP.NET Core MVC, Razor Pages, Blazor Server) with cookie-based authentication and Auth0.AspNetCore.Authentication integration including login/callback/profile/logout flows. | 3 / 3 |
Completeness | Clearly answers both what ('integrates Auth0.AspNetCore.Authentication for server-rendered apps with login/callback/profile/logout flows') and when ('Use when adding login, logout, and user profile to an ASP.NET Core MVC, Razor Pages, or Blazor Server web application using cookie-based authentication'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'login', 'logout', 'user profile', 'ASP.NET Core', 'MVC', 'Razor Pages', 'Blazor Server', 'cookie-based authentication', 'Auth0', 'callback'. These are all terms a developer would naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Auth0 authentication specifically for ASP.NET Core server-rendered apps with cookie-based auth. The combination of Auth0 + ASP.NET Core + server-rendered + cookie-based creates a very specific trigger profile unlikely to conflict with other authentication or web framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a thorough, highly actionable skill with excellent executable code examples covering multiple ASP.NET Core application types. The workflow is well-sequenced with important gotchas clearly highlighted. However, the skill is overly long due to covering three variants inline, duplicating code in the Quick Reference section, and including large reference tables that could be offloaded to bundle files — reducing token efficiency.
Suggestions
Move the Blazor Server and Razor Pages variants into separate reference files to reduce the main skill's token footprint, keeping only the MVC workflow inline with pointers to variants.
Remove the Quick Reference section at the bottom — it duplicates code already shown in the numbered workflow steps and adds ~40 lines of redundant content.
Trim the Key SDK Methods table, which largely restates what the code examples already demonstrate; keep only methods not shown in the workflow code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but verbose — it covers MVC, Blazor Server, and Razor Pages variants with full code blocks, a large common mistakes table, and a key SDK methods table that largely repeats what's already shown in the code examples. The Quick Reference section at the end duplicates code already presented in the workflow. Some explanatory sentences (e.g., explaining what Domain/ClientId are) are unnecessary for Claude. | 2 / 3 |
Actionability | All code examples are fully executable and copy-paste ready — complete controller classes, Program.cs configuration, Razor views, appsettings.json, and bash commands. Every step includes concrete, specific code with correct using statements and method signatures. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (install → configure credentials → configure dashboard → register in Program.cs → create controller → create views → update nav → test) with numbered steps. Critical ordering constraints are explicitly called out (UseAuthentication before UseAuthorization), and the common mistakes table serves as a validation checklist. The test step provides a concrete verification action. | 3 / 3 |
Progressive Disclosure | The skill references three detailed documentation files (references/setup.md, references/integration.md, references/api.md) which is good structure, but no bundle files are provided so these references are unverifiable. The main file itself is quite long with inline content for three variants (MVC, Blazor Server, Razor Pages) plus large reference tables that could have been moved to reference files, making the main skill heavier than ideal. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- auth0/agent-skills
- Commit
bdf0dc2
- 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.