auth0-react-native
Use when adding authentication to React Native or Expo mobile apps (iOS/Android) with biometric support - integrates react-native-auth0 SDK with native deep linking
84
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 is a strong description that clearly communicates when to use the skill and targets a specific niche (Auth0 authentication for React Native/Expo). It includes excellent trigger terms and an explicit 'Use when' clause. The main weakness is that it could list more concrete actions (e.g., configure login flows, set up biometric prompts, handle token storage) to improve specificity.
Suggestions
Add more concrete actions like 'configure login flows, set up biometric prompts, handle token storage and refresh' to improve specificity beyond just 'integrates SDK'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (authentication in React Native/Expo mobile apps) and mentions some specific capabilities (biometric support, react-native-auth0 SDK, native deep linking), but doesn't list multiple concrete actions like 'configure login flows, set up biometric authentication, handle token refresh'. | 2 / 3 |
Completeness | Explicitly answers both 'what' (integrates react-native-auth0 SDK with native deep linking and biometric support) and 'when' (starts with 'Use when adding authentication to React Native or Expo mobile apps'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'authentication', 'React Native', 'Expo', 'mobile apps', 'iOS/Android', 'biometric', 'react-native-auth0', 'deep linking'. These cover a wide range of terms a developer would naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Auth0-based authentication specifically for React Native/Expo with biometric support. The combination of Auth0 + React Native + biometric + deep linking is very specific and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 good progressive disclosure. The main workflow provides complete, executable code for each step with platform-specific configurations. The primary weakness is the lack of validation checkpoints in a multi-step native configuration process, and some content redundancy between the workflow steps and the Quick Reference section.
Suggestions
Add explicit validation checkpoints after native platform configuration (Step 3), such as 'Verify: rebuild the app and confirm no build errors before proceeding' — native config mistakes are the most common failure point.
Consider removing or significantly trimming the Quick Reference section, as it largely duplicates information already demonstrated in the workflow steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some redundancy — the Quick Reference section largely repeats what's already shown in the workflow steps, and the 'When NOT to Use' section is somewhat verbose. The native platform configuration blocks are necessarily long but could potentially reference a setup guide instead of being inline. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code for every step — from installation commands to complete TypeScript components with Auth0Provider setup and useAuth0 hook usage. Platform-specific configuration includes exact XML/JSON snippets with clear file paths. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (1-6), but there are no explicit validation checkpoints between steps. For a multi-step process involving native platform configuration (which is fragile and error-prone), there should be verification steps after configuring iOS/Android/Expo and before moving to the code integration step. The 'Common Mistakes' table partially compensates but is reactive rather than proactive. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise quick-start workflow inline and clear one-level-deep references to setup guide, patterns guide, and API reference. The detailed documentation section is well-signaled with descriptive labels, and advanced topics like biometric auth and token refresh are appropriately linked to reference files. | 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.