Skip to main content
clerk-hello-world Create your first authenticated request with Clerk.
Use when making initial API calls, testing authentication,
or verifying Clerk integration works correctly.
Trigger with phrases like "clerk hello world", "first clerk request",
"test clerk auth", "verify clerk setup".
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill clerk-hello-worldEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Explorador de archivos
2 archivos Ocupaciones relacionadas SOC
Basado en la clasificación ocupacional SOC
name clerk-hello-world description Create your first authenticated request with Clerk.
Use when making initial API calls, testing authentication,
or verifying Clerk integration works correctly.
Trigger with phrases like "clerk hello world", "first clerk request",
"test clerk auth", "verify clerk setup".
allowed-tools Read, Write, Edit, Bash(npm:*), Grep version 1.14.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","clerk","api","testing","authentication"] compatibility Designed for Claude Code, also compatible with Codex and OpenClaw
Clerk Hello World
Overview
Make your first authenticated requests using Clerk across server components, client components, API routes, and server actions. Validates your Clerk integration end-to-end.
Prerequisites
Clerk SDK installed (clerk-install-auth completed)
Environment variables configured (NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY, CLERK_SECRET_KEY)
ClerkProvider wrapping application root
Middleware configured at project root
Instructions
Step 1: Server Component — auth() and currentUser()
import { auth, currentUser } from '@clerk/nextjs/server'
import { redirect } from 'next/navigation'
export default async function DashboardPage (const { userId } = await auth ()
if (!userId) redirect ('/sign-in' )
const user = await currentUser ()
return (
<div >
<h1 > Hello, {user?.firstName || 'User'}!</h1 >
<p > User ID: {userId}</p >
<p > Email: {user?.emailAddresses[0]?.emailAddress}</p >
<p >
</p >
</div >
Key distinction: auth() is cheap (JWT parsing, no network). currentUser() is expensive (Backend API call, rate-limited). Prefer auth() when you only need userId, orgId, or sessionClaims.
Step 2: Protected API Route
import { auth } from '@clerk/nextjs/server'
export async function GET (const { userId, orgId, sessionClaims } = await auth ()
if (!userId) {
return Response .json ({ error : 'Unauthorized' }, { status : 401 })
}
return Response .json ({
message : 'Hello from Clerk!' ,
userId,
orgId : orgId || null ,
sessionId : sessionClaims?.sid ,
timestamp : new Date ().toISOString (),
})
}
Step 3: Client Component with Hooks 'use client'
import { useUser, useAuth, useClerk } from '@clerk/nextjs'
export function AuthTest (const { user, isLoaded, isSignedIn } = useUser ()
const { getToken, signOut } = useAuth ()
const { openUserProfile } = useClerk ()
if (!isLoaded) return <div > Loading...</div > if (!isSignedIn) return <div > Not signed in</div > const testAPI = async (const token = await getToken ()
const res = await fetch ('/api/hello' , {
headers : { Authorization : `Bearer ${token} ` },
})
const data = await res.json ()
console .log ('API response:' , data)
}
return (
<div >
<p > Signed in as: {user.primaryEmailAddress?.emailAddress}</p >
<img src ={user.imageUrl} alt ="Avatar" width ={48} height ={48} />
<div className ="flex gap-2 mt-4" >
<button onClick ={testAPI} > Test API</button >
<button onClick ={() => openUserProfile()}>Profile</button >
<button onClick ={() => signOut()}>Sign Out</button >
</div >
</div >
Step 4: Server Action with Auth
'use server'
import { auth } from '@clerk/nextjs/server'
export async function greetUser (const { userId } = await auth ()
if (!userId) throw new Error ('Unauthorized' )
return { greeting : `Hello user ${userId} !` , timestamp : new Date ().toISOString () }
}
'use client'
import { greetUser } from '@/app/actions'
import { useState } from 'react'
export function GreetingButton (const [msg, setMsg] = useState<string | null >(null )
return (
<div >
<button onClick ={async () => {
const result = await greetUser()
setMsg(result.greeting)
}}>
Get Server Greeting
</button >
{msg && <p > {msg}</p > }
</div >
Step 5: Express.js Hello World import express from 'express'
import { clerkMiddleware, requireAuth, getAuth } from '@clerk/express'
const app = express ()
app.use (clerkMiddleware ())
app.get ('/api/hello' , (req, res ) => {
const { userId } = getAuth (req)
res.json ({
message : userId ? `Hello user ${userId} !` : 'Hello anonymous!' ,
authenticated : !!userId,
})
})
app.get ('/api/me' , requireAuth (), (req, res ) => {
const { userId, orgId } = getAuth (req)
res.json ({ userId, orgId })
})
app.listen (3001 )
Error Handling Error Cause Solution userId is nullUser not authenticated Redirect to /sign-in or check middleware covers route currentUser() returns nullSession expired or invalid Refresh page; ensure middleware is running 401 from API route Token missing or expired Include Authorization: Bearer <token> header Hydration mismatch Server/client state differs Guard client components with isLoaded check auth() was called but Clerk can't detect clerkMiddleware()Middleware not in project root Move middleware.ts out of app/ to project root
Enterprise Considerations
Use auth() over currentUser() in hot paths to avoid Backend API rate limits
Deduplicate currentUser() calls with React's cache() function across server components in the same request
For microservices, pass Clerk JWTs between services and verify with @clerk/backend or @clerk/express
Session token v2 (default since April 2025) uses a more compact format -- ensure downstream JWT consumers are updated
Custom session claims can be set in Dashboard > Sessions > Customize session token (limit: 1.2KB)
Resources
Next Steps Proceed to clerk-local-dev-loop for local development workflow setup.
Output
Minimal Clerk "hello world" that signs in a user and shows identity on a protected page
Exact install + env steps for the chosen framework
Next-step links into deeper clerk-pack skills (webhooks, RBAC, production checklist)
Examples
Next.js hello world User: Smallest possible Clerk + Next.js demo with a protected /me page.
Skill: scaffolds packages, middleware, sign-in UI, and /me reading user id.
Verify keys are live User: Confirm publishable + secret keys work against Clerk API.
Skill: runs a minimal session/user fetch and reports success or key-mismatch errors.
Más de este repositorio Implement user sign-up and sign-in flows with Clerk.
Use when building authentication UI, customizing sign-in experience,
or implementing OAuth social login.
Trigger with phrases like "clerk sign-in", "clerk sign-up",
"clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk.
Use when managing user sessions, configuring route protection,
or implementing token refresh and custom JWT templates.
Trigger with phrases like "clerk session", "clerk middleware",
"clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management.
Use when implementing SSO integration, configuring role-based permissions,
or setting up organization-level controls.
Trigger with phrases like "clerk SSO", "clerk RBAC",
"clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
