Skip to main content 홈 크리에이터 jeremylongshore tons-of-skills-marketplace clerk-hello-world
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".
설치로 이동 Skills Marketplace 커뮤니티가 만든 AI 스킬을 발견하고 탐색하세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill clerk-hello-world명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Zip 다운로드 다운로드 중... 이 저장소의 다른 Skills langchain-deploy-integration Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".
langchain-langgraph-agents Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".
langchain-langgraph-human-in-loop Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before /
interrupt_after and Command(resume=...) — JSON-serializable state, clean
resume semantics, and UI wiring for approval decisions. Use when adding an
approval gate before an expensive tool call, wiring a Slack/web UI for agent
approvals, or debugging a graph that crashes on interrupt.
Trigger with "langgraph human in loop", "langgraph interrupt_before",
"langgraph approval flow", "Command resume", "langgraph HITL".
jeremylongshore
jeremylongshore/tons-of-skills-marketplace
GitHub 저장소 열기 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
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}
Created: {user?.createdAt ? new Date(user.createdAt).toLocaleDateString() : 'N/A'}
)
}
</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.