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.
94
92%
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 migration to Auth0), lists specific capabilities, and includes explicit trigger conditions. It uses third person voice appropriately and provides natural keywords that users would actually say when needing this skill. The description effectively distinguishes itself from general authentication skills by focusing specifically on the migration use case.
| 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 or switching from an existing auth provider... to Auth0'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'migrating', 'switching', 'auth provider', plus specific provider names (Firebase, Cognito, Supabase, Clerk), and technical terms like 'JWT validation' that users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche - specifically about migrating TO Auth0 FROM other providers. The combination of source providers and Auth0 as target creates a distinct trigger that wouldn't conflict with general auth skills or other provider-specific skills. | 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, providing a clear roadmap for complex auth migrations. The content is appropriately concise for an overview document, though it relies heavily on reference files for actionable code examples, which slightly reduces immediate actionability within the main skill file itself.
Suggestions
Add one complete, executable code example for the most common migration path (e.g., Firebase to Auth0 React) directly in the main skill to improve immediate actionability
Include a minimal but complete users.json example showing the required format for the bulk import command
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference, avoiding explanations of basic concepts Claude already knows, and delegating detailed content to reference files appropriately. | 3 / 3 |
Actionability | Provides some concrete guidance like the CLI command and TypeScript snippet, but most actionable content is delegated to reference files. The main skill lacks complete executable examples for core migration tasks. | 2 / 3 |
Workflow Clarity | Clear 4-step migration workflow with explicit phases for gradual migration. Includes validation checkpoints (Step 0 detection, phased approach with parallel auth), and a troubleshooting table for error recovery. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview, well-organized sections, and one-level-deep references to detailed documentation. Links are clearly signaled with descriptive anchors pointing to specific sections in reference files. | 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.
fbcbfb1
Table of Contents
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.