Use when adding authentication or login to any app - detects your stack (React, Next.js, Vue, Nuxt, Angular, Express, Fastify, FastAPI, ASP.NET Core, React Native, Expo, Android, Swift), sets up an Auth0 account if needed, and routes to the correct SDK setup workflow.
88
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 a strong skill description that clearly communicates what the skill does (detect stack, set up Auth0, route to SDK workflow), when to use it (adding authentication or login), and for which technologies. It uses natural trigger terms and has a clear niche that distinguishes it from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: detects stack, sets up Auth0 account, routes to correct SDK setup workflow. Also enumerates specific supported frameworks (React, Next.js, Vue, Nuxt, Angular, Express, Fastify, FastAPI, ASP.NET Core, React Native, Expo, Android, Swift). | 3 / 3 |
Completeness | Explicitly answers both 'what' (detects stack, sets up Auth0 account, routes to SDK setup) and 'when' ('Use when adding authentication or login to any app'). The 'Use when...' clause is present and clear. | 3 / 3 |
Trigger Term Quality | Includes highly natural trigger terms users would say: 'authentication', 'login', 'Auth0', plus all the specific framework names. A user asking about adding login or authentication to their app would naturally use these terms. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Auth0 authentication setup across specific frameworks. The combination of 'Auth0' + 'authentication/login' + specific stack detection makes it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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 routing/quickstart skill that effectively detects frameworks and directs users to appropriate sub-skills. Its main strengths are actionable CLI commands and excellent progressive disclosure to reference materials. Weaknesses include content redundancy (framework lists repeated 3 times) and missing validation checkpoints in the workflow.
Suggestions
Add a validation step after app creation (e.g., `auth0 apps show <app-id>` to confirm credentials are correct before proceeding to SDK setup)
Consolidate the three repeated framework listings (detection table, Tier 1 list, Related Skills) — the detection table and Related Skills section largely duplicate Step 4's Tier 1 list
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes redundancy — the framework list appears in the detection table, then again in Tier 1 listing, and again in Related Skills. The Common Mistakes table and Tier 2 external links add bulk that could be in reference files. Some sections like 'Related Skills' largely duplicate Step 4. | 2 / 3 |
Actionability | Provides fully executable CLI commands for installation, login, app creation by type, and framework detection. The commands are copy-paste ready with appropriate flags and placeholders. The detection table gives concrete patterns to match against. | 3 / 3 |
Workflow Clarity | The 4-step workflow is clearly sequenced and logical. However, there are no validation checkpoints — after creating an Auth0 app, there's no verification step (e.g., confirming the app was created successfully, testing the credentials). For an operation involving account setup and credential management, explicit validation steps would be expected. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview that routes to framework-specific skills and well-organized reference links (CLI, environments, concepts) that are one level deep and clearly signaled with anchor links. | 3 / 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_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
d85127d
Table of Contents
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.