Skillshub clerk-setup
Add Clerk authentication to any project by following the official quickstart guides.
install
source · Clone the upstream repo
git clone https://github.com/ComeOnOliver/skillshub
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ComeOnOliver/skillshub "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/Harmeet10000/skills/clerk-setup" ~/.claude/skills/comeonoliver-skillshub-clerk-setup && rm -rf "$T"
manifest:
skills/Harmeet10000/skills/clerk-setup/SKILL.mdsource content
Adding Clerk
This skill sets up Clerk for authentication by following the official quickstart documentation.
Quick Reference
| Step | Action |
|---|---|
| 1. Detect framework | Check dependencies |
| 2. Fetch quickstart | Use WebFetch on the appropriate docs URL |
| 3. Follow instructions | Execute the steps from the official guide |
| 4. Get API keys | From dashboard.clerk.com |
Framework Detection
Check
package.json to identify the framework:
| Dependency | Framework | Quickstart URL |
|---|---|---|
| Next.js | |
| Remix | |
| Astro | |
| Nuxt | |
| React Router | |
| TanStack Start | |
(no framework) | React SPA | |
| Vue | |
| Express | |
| Fastify | |
| Expo | |
For other platforms:
- Chrome Extension:
https://clerk.com/docs/chrome-extension/getting-started/quickstart - Android:
https://clerk.com/docs/android/getting-started/quickstart - iOS:
https://clerk.com/docs/ios/getting-started/quickstart - Vanilla JavaScript:
https://clerk.com/docs/js-frontend/getting-started/quickstart
Decision Tree
User Request: "Add Clerk" / "Add authentication" │ ├─ Read package.json │ ├─ Existing auth detected? │ │ │ ├─ YES → Audit current auth → Create migration plan │ │ → See "Migrating from Another Auth Provider" │ │ │ └─ NO → Fresh install │ ├─ Identify framework from dependencies │ ├─ WebFetch the appropriate quickstart URL │ └─ Follow the official instructions step-by-step
Setup Process
1. Detect the Framework
Read the project's
package.json and match dependencies to the table above.
2. Fetch the Quickstart Guide
Use WebFetch to retrieve the official quickstart for the detected framework:
WebFetch: https://clerk.com/docs/{framework}/getting-started/quickstart Prompt: "Extract the complete setup instructions including all code snippets, file paths, and configuration steps."
3. Follow the Instructions
Execute each step from the quickstart guide:
- Install the required packages
- Set up environment variables
- Add the provider/middleware
- Create sign-in/sign-up routes if needed
- Test the integration
4. Get API Keys
Two paths for development API keys:
Keyless (Automatic)
- On first SDK initialization, Clerk auto-generates dev keys and shows "Claim your application" popover
- No manual key setup required—keys are created and injected automatically
- Simplest path for new projects
Manual (Dashboard)
- Get keys from dashboard.clerk.com if Keyless doesn't trigger
- Publishable Key: Starts with
orpk_test_pk_live_ - Secret Key: Starts with
orsk_test_sk_live_ - Set as environment variables:
andNEXT_PUBLIC_CLERK_PUBLISHABLE_KEYCLERK_SECRET_KEY
Migrating from Another Auth Provider
If the project already has authentication, create a migration plan before replacing it.
Detect Existing Auth
Check
package.json for existing auth libraries:
/next-auth
→ NextAuth/Auth.js@auth/core
→ Supabase Auth@supabase/supabase-js
/firebase
→ Firebase Authfirebase-admin
→ AWS Cognito@aws-amplify/auth
/auth0
→ Auth0@auth0/nextjs-auth0
→ Passport.jspassport- Custom JWT/session implementation
Migration Process
-
Audit current auth - Identify all auth touchpoints:
- Sign-in/sign-up pages
- Session/token handling
- Protected routes and middleware
- User data storage (database tables, external IDs)
- OAuth providers configured
-
Create migration plan - Consider:
- User data export - Export users and import via Clerk's Backend API
- Password hashes - Clerk can upgrade hashes to Bcrypt transparently
- External IDs - Store legacy user IDs as
in Clerkexternal_id - Session handling - Existing sessions will terminate on switch
-
Choose migration strategy:
- Big bang - Switch all users at once (simpler, requires maintenance window)
- Trickle migration - Run both systems temporarily (lower risk, higher complexity)
Migration Reference
- Migration Overview: https://clerk.com/docs/guides/development/migrating/overview
Common Pitfalls
| Level | Issue | Solution |
|---|---|---|
| CRITICAL | Missing on | In Next.js 15+, is async: |
| CRITICAL | Exposing | Never use secret key in client code; only keys are safe |
| HIGH | Missing middleware matcher | Include API routes: `matcher: ['/((?!.\.. |
| HIGH | ClerkProvider not at root | Must wrap entire app in root layout/App component |
| HIGH | Auth routes not public | Allow , in middleware config |
| HIGH | Landing page requires auth | To keep "/" public, exclude it: `matcher: ['/((?!.\.. |
| MEDIUM | Wrong import path | Server code uses , client uses |
See Also
- Custom sign-in/up componentscustom-flows/
- Webhook → database syncsyncing-users/
- B2B multi-tenant organizationsmanaging-orgs/
- E2E testing setuptesting/
- Advanced Next.js patternsnextjs-patterns/
Documentation
- Quickstart Overview: https://clerk.com/docs/getting-started/quickstart/overview
- Migration Guide: https://clerk.com/docs/guides/development/migrating/overview
- Full Documentation: https://clerk.com/docs