auth0-migration
Use when migrating or switching from an existing auth provider (Firebase, Cognito, Supabase, Clerk, custom auth) to Auth0 - covers bulk user import, gradual migration strategies, code migration patterns, and JWT validation updates.
67
81%
Does it follow best practices?
Impact
—
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 an excellent skill description that clearly defines its scope (auth provider migration to Auth0), lists concrete capabilities, and includes strong trigger terms with named providers. The explicit 'Use when' clause with specific scenarios makes it easy for Claude to select this skill appropriately. It follows the third-person voice convention and is concise without being vague.
| 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 | Clearly answers both what (bulk user import, gradual migration strategies, code migration patterns, JWT validation updates) and when (migrating or switching from an existing auth provider to Auth0) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'migrating', 'switching', 'auth provider', and specific provider names (Firebase, Cognito, Supabase, Clerk, custom auth, Auth0). Users searching for migration help would naturally use these terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive - targets a very specific niche of migrating TO Auth0 FROM other named providers. The combination of migration context + specific source providers + Auth0 destination makes it unlikely to conflict with general auth skills or individual provider skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%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-organized migration guide with excellent workflow clarity — the step-by-step process and phased gradual migration strategy are clear and logical. However, the skill leans heavily on reference files for actionable content while the main body serves primarily as a table of contents, and the repeated reference link listings add unnecessary bulk. The skill would benefit from more inline executable examples and deduplication of reference links.
Suggestions
Add more inline executable examples (e.g., a complete user JSON format snippet, an actual export command for at least one provider) rather than deferring nearly all actionable content to reference files.
Consolidate reference links to appear in one place — either within the workflow steps OR in the Reference Documentation section, not both.
Include a brief validation/verification step after user import (e.g., checking import job status, verifying a sample user can log in) to strengthen the workflow with explicit checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but has some redundancy — the reference links are listed multiple times (Steps 1-4 and again in the Reference Documentation section), and the Related Skills section partially duplicates the list already given in Step 3. The detection table and migration phases are well-structured but could be tighter. | 2 / 3 |
Actionability | The skill provides one concrete CLI command for user import and a brief TypeScript snippet for parallel auth, but most actionable content is deferred to reference files. The main body is more of a navigation guide than executable guidance — key details like the user JSON format, actual export commands, and code migration patterns are all behind references. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced (Steps 0-4) with a well-defined gradual migration strategy (Phases 1-4). Step 0 includes a decision point for the user, the gradual migration includes explicit phases with clear transitions, and the common migration issues table serves as a troubleshooting checkpoint. The phased approach with parallel auth → new users → forced migration → cleanup is a strong feedback loop. | 3 / 3 |
Progressive Disclosure | The skill references detailed files like references/user-import.md and references/code-patterns.md with well-signaled anchor links, which is good structure. However, no bundle files were provided, so these references cannot be verified. Additionally, the same reference links appear in multiple places (within steps AND in the Reference Documentation section), creating redundant navigation that clutters the overview. | 2 / 3 |
Total | 9 / 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.