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.
87
85%
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 an excellent skill description that clearly defines its scope (auth provider migration to Auth0), lists concrete capabilities, and includes an explicit 'Use when' trigger clause with natural keywords. The enumeration of specific source providers (Firebase, Cognito, Supabase, Clerk) greatly enhances both trigger term quality and distinctiveness. 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' (covers bulk user import, gradual migration strategies, code migration patterns, JWT validation updates) and 'when' (explicitly starts with 'Use when migrating or switching from an existing auth provider... to Auth0'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'migrating', 'switching', 'auth provider', and names specific providers (Firebase, Cognito, Supabase, Clerk, custom auth) plus Auth0. Terms like 'bulk user import', 'JWT validation' are exactly what users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive - specifically scoped to migrating TO Auth0 FROM named providers. The combination of migration context + specific source providers + Auth0 target creates a clear niche unlikely to conflict with general auth setup or other auth-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%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 with excellent progressive disclosure and clear workflow sequencing. Its main weakness is that most actionable content lives in reference files, making the main document more of a routing table than a hands-on guide. The reference links are duplicated between the workflow steps and the reference section, adding unnecessary tokens.
Suggestions
Add a few more inline executable examples (e.g., a minimal users.json format snippet, a complete export command for at least one provider) so the main document is actionable without requiring reference file access.
Remove the duplicate 'Reference Documentation' section at the bottom since the same links are already provided inline within each workflow step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but has some redundancy — the reference links are listed multiple times (once inline in the workflow steps and again in the 'Reference Documentation' section). The detection table and migration phases are useful but could be tighter. Some sections like 'When NOT to Use' explain things Claude could infer. | 2 / 3 |
Actionability | The skill provides one concrete CLI command and one TypeScript snippet, but most actionable content is deferred to reference files. The main document is more of a navigation hub than an executable guide — key details like user JSON format, export commands, and SDK setup are all behind links. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced (Steps 0-4) with a well-structured gradual migration strategy (Phases 1-4). The common migration issues table serves as a troubleshooting checkpoint. The detection step and decision prompt at Step 0 provide a good validation/branching point before proceeding. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the main skill provides a clear overview and workflow, with well-signaled one-level-deep references to user-import.md and code-patterns.md using anchor links. Content is appropriately split between overview and detailed 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
d85127d
- 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.