auth0-migration
Use when migrating from existing auth providers (Firebase, Cognito, Supabase, custom auth) to Auth0 - covers bulk user import, gradual migration strategies, code migration patterns, and JWT validation updates
92
Does it follow best practices?
Evaluation — 85%
↑ 1.04xAgent success when using this skill
Validation for skill structure
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 well-crafted skill description that excels across all dimensions. It opens with an explicit 'Use when' clause, names specific competing auth providers as trigger terms, and lists concrete migration-related actions. The description is concise yet comprehensive, making it easy for Claude to select this skill precisely when users discuss auth migration scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'bulk user import, gradual migration strategies, code migration patterns, and JWT validation updates' - these are clear, actionable capabilities. | 3 / 3 |
Completeness | Explicitly answers both what (bulk user import, gradual migration strategies, code migration patterns, JWT validation updates) AND when ('Use when migrating from existing auth providers... to Auth0') with clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'migrating', 'Firebase', 'Cognito', 'Supabase', 'custom auth', 'Auth0', 'bulk user import', 'JWT' - these are exactly what developers would mention when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche - specifically targets Auth0 migration from named competitors (Firebase, Cognito, Supabase). The combination of source providers + Auth0 destination + migration-specific actions creates a clear, non-conflicting scope. | 3 / 3 |
Total | 12 / 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 migration guide that excels at progressive disclosure and workflow clarity. The content efficiently organizes a complex multi-step process with clear phases and extensive cross-references. The main weakness is that actionable code examples are sparse in the main file, relying heavily on reference documents for concrete implementation details.
Suggestions
Add one complete, executable code example inline (e.g., a full user export script for the most common provider) rather than delegating all code to references
Include a concrete validation step in the workflow, such as 'Verify import: auth0 api get users --q email:test@example.com' to confirm users imported correctly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Tables and bullet points convey information densely, and there's no padding or unnecessary context about what authentication is or how providers work. | 3 / 3 |
Actionability | Provides some concrete guidance like the CLI command and TypeScript snippet, but most actionable content is delegated to reference files. The inline examples are minimal and the gradual migration code is more illustrative than copy-paste ready for real implementation. | 2 / 3 |
Workflow Clarity | Clear 4-step migration workflow with explicit phases for gradual migration. The numbered steps, phase breakdown, and common issues table provide excellent sequencing. Validation is implicit through the phased approach with parallel auth before cleanup. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview pointing to one-level-deep references. Links to specific sections in reference files are well-organized and clearly signaled. The skill appropriately keeps the main file as an overview while delegating detailed examples to reference documents. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.