auth0-react
Use when adding authentication to React applications (login, logout, user sessions, protected routes) - integrates @auth0/auth0-react SDK for SPAs with Vite or Create React App
88
86%
Does it follow best practices?
Impact
Pending
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 a strong skill description that clearly communicates what it does (Auth0 authentication integration for React SPAs), when to use it (adding login/logout/sessions/protected routes), and includes specific technical context (SDK name, build tools). It uses proper third-person voice and includes natural trigger terms that developers would use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'adding authentication', 'login, logout, user sessions, protected routes', and specifies the SDK (@auth0/auth0-react) and build tools (Vite, Create React App). | 3 / 3 |
Completeness | Clearly answers both what (integrates @auth0/auth0-react SDK for authentication including login, logout, user sessions, protected routes) and when ('Use when adding authentication to React applications') with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'authentication', 'login', 'logout', 'user sessions', 'protected routes', 'React', 'auth0', 'SPA', 'Vite', 'Create React App'. These are all terms a developer would naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Auth0 SDK integration in React SPAs with specific build tools. Unlikely to conflict with general authentication skills, non-React auth skills, or other React skills that don't involve authentication. | 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 skill with strong actionability and excellent progressive disclosure. The quick start workflow provides concrete, executable code for both Vite and CRA setups. Main weaknesses are some redundancy in the common mistakes table and quick reference sections, and the lack of explicit validation checkpoints in the workflow (e.g., what specifically to verify after testing).
Suggestions
Add explicit validation checkpoints to Step 5 (e.g., 'Verify: clicking Login redirects to Auth0, after login user.name displays, logout clears the session')
Deduplicate common mistakes — merge 'Missing Auth0Provider wrapper' and 'Provider not at root level' into one entry, and consolidate the env var prefix mentions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some content that could be tightened. The 'When NOT to Use' section and the extensive MFA error types in the quick reference add bulk. The common mistakes table is thorough but some entries (like 'Provider not at root level' vs 'Missing Auth0Provider wrapper') are near-duplicates. The env var prefix distinction is repeated in multiple places. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code for every step: install command, env file setup for both Vite and CRA, complete Auth0Provider configuration, and a working LoginButton component. Commands are specific and concrete. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced and logical. However, there are no explicit validation checkpoints — Step 5 just says 'test the login flow' without specifying what to verify (e.g., check redirect works, verify user object populates, confirm logout clears session). For an auth integration that can fail silently, explicit verification steps would be valuable. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The main file provides a concise quick start, then clearly signals one-level-deep references for setup, integration, and API details. The 'Detailed Documentation' section has well-labeled links with brief descriptions of what each reference contains. | 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 | |
- Repository
- auth0/agent-skills
- Commit
9777204
- 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.