Migrate users and authentication flows from existing auth providers to Auth0.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionauth0-migrationExecute the skills CLI command in your project's root directory to begin installation:
Fetches auth0-migration from auth0/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate auth0-migration. Access via /auth0-migration in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
14
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
14
stars
Migrate users and authentication flows from existing auth providers to Auth0.
auth0-quickstart for new projects without existing usersCheck if the project already has authentication:
Search for common auth-related patterns in the codebase:
| Pattern | Indicates |
|---|---|
signInWithEmailAndPassword, onAuthStateChanged |
Firebase Auth |
useUser, useSession, isSignedIn |
Existing auth hooks |
passport.authenticate, LocalStrategy |
Passport.js |
authorize, getAccessToken, oauth |
OAuth/OIDC |
JWT, jwt.verify, jsonwebtoken |
Token-based auth |
/api/auth/, /login, /callback |
Auth routes |
If existing auth detected, ask:
I detected existing authentication in your project. Are you:
- Migrating to Auth0 (replace existing auth)
- Adding Auth0 alongside (keep both temporarily)
- Starting fresh (remove old auth, new Auth0 setup)
Export users from your current provider. See User Import Guide for detailed instructions:
Required data per user:
Import users via Dashboard, CLI, or Management API.
Quick start:
# Via Auth0 CLI
auth0 api post "jobs/users-imports" \
--data "connection_id=con_ABC123" \
--data "[email protected]"
For detailed instructions:
Update your application code to use Auth0 SDKs.
See Code Migration Patterns for detailed before/after examples:
Frontend:
Backend:
Provider-Specific:
After migrating code, use framework-specific skills:
auth0-react for React applicationsauth0-nextjs for Next.js applicationsauth0-vue for Vue.js applicationsauth0-angular for Angular applicationsauth0-express for Express.js applicationsauth0-react-native for React Native/Expo applicationsIf your API validates JWTs, update to validate Auth0 tokens.
Key differences:
https://YOUR_TENANT.auth0.com/https://YOUR_TENANT.auth0.com/.well-known/jwks.jsonSee JWT Validation Examples for:
For production applications with active users, use a phased approach:
Support both Auth0 and legacy provider simultaneously:
// Support both providers during migration
const getUser = async () => {
// Try Auth0 first
const auth0User = await getAuth0User();
if (auth0User) return auth0User;
// Fall back to legacy provider
return await getLegacyUser();
};
| Issue | Solution |
|---|---|
| Password hashes incompatible | Use Auth0 custom DB connection with lazy migration |
| Social logins don't link | Configure same social connection, users auto-link by email |
| Custom claims missing | Add claims via Auth0 Actions |
| Token format different | Update API to validate RS256 JWTs with Auth0 issuer |
| Session persistence | Auth0 uses rotating refresh tokens; update token storage |
| Users must re-login | Expected for redirect-based auth; communicate to users |
Complete guide to exporting and importing users:
Before/after examples for all major frameworks:
auth0-quickstart - Initial Auth0 setup after migrationauth0-react - React SPA integrationauth0-nextjs - Next.js integrationauth0-vue - Vue.js integrationauth0-angular - Angular integrationauth0-express - Express.js integrationauth0-react-native - React Native/Expo integrationMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Registry listing for auth0-migration matched our evaluation — installs cleanly and behaves as described in the markdown.
auth0-migration reduced setup friction for our internal harness; good balance of opinion and flexibility.
auth0-migration has been reliable in day-to-day use. Documentation quality is above average for community skills.
auth0-migration fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: auth0-migration is the kind of skill you can hand to a new teammate without a long onboarding doc.
auth0-migration has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in auth0-migration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend auth0-migration for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
auth0-migration fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in auth0-migration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 71