clerk-setup Skill for Claude: What It Does and How to Install It

Makes Claude add Clerk authentication to a project, or scaffold a new app with it, using the Clerk CLI.

Installs: 57.9K; on skills.sh
Stars: 89; on GitHub
Files: 1; besides SKILL.md
Updated: Oct 2026; last repo commit

This is Clerk's own setup skill. After you say yes to a short checklist, Claude runs npx -y clerk@latest init, which detects your framework, installs the SDK and configures the provider, middleware, auth routes and environment. It can scaffold a new app in an empty folder, and works without a Clerk account by using temporary development keys.

It also covers claiming the app, changing sign-in options and a production deploy. The folder holds SKILL.md and an evals file of sample prompts, and bundles no scripts. Read the safety box first: it edits your project.

Good for

Developers adding sign-in and user management to a new or existing web app
People starting a new app on Next.js, React, Astro, Nuxt, Vue, Expo or similar with auth built in
Teams moving from another auth system who want a plan first

Install clerk-setup

Claude Code

Copy this prompt.

Install the clerk-setup skill in Claude Code. Run this command:

/plugin marketplace add clerk/skills
/plugin install clerk@clerk-skills

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Pick one route. The Clerk plugin installs all 20 skills in the repo plus the hosted Clerk MCP server (mcp.clerk.com/mcp) from its .mcp.json; the skills CLI routes install skills only. Per the README, the clerk plugin replaces the earlier clerk-skills@clerk Codex plugin and the earlier core, frameworks, features and mobile Copilot plugins, and Copilot may leave clerk@clerk-skills disabled until you run copilot plugin enable clerk@clerk-skills.

From the project README. Source.

What's in the skill

When it loads

Set up Clerk authentication in any project with the Clerk CLI and official framework quickstarts. Use when adding Clerk, initializing Clerk, scaffolding a new app with Clerk, or migrating an existing authentication system to Clerk.

Sections in SKILL.md

Before you start
Existing authentication
Existing Clerk projects
Use an existing Clerk application (optional)
Step 1a: Existing project without Clerk
Step 1b: Empty directory
Step 1c: Accountless development keys
Step 2: Fall back to docs when init is incomplete
Step 3: Add visible auth controls
Step 4: Verify
Step 5: If using shadcn/ui
Critical rules
After setup

Key facts

Author: Clerk (vendor's own repo)
Repo: clerk/skills
License: MIT (README, plugin.json and the SKILL.md frontmatter say MIT; the repo has no LICENSE file)
Installs on skills.sh: 57,857 (Nov 2, 2026)
GitHub stars: 89 for the whole repo (Nov 2, 2026)
Last repo commit: Oct 30, 2026
Audits on skills.sh: Gen Agent Trust Hub: pass, Socket: pass, Snyk: pass
What it includes: 2 files: SKILL.md and evals/evals.json (sample prompts). It bundles no scripts
Part of: Plugin clerk: 20 skills plus the Clerk MCP server
Needs: Node.js 20.9.0 or later; the Clerk CLI via npx

What it includes

Shows what it will do and waits for your yes before touching anything
It lists three steps: set up Clerk or scaffold a new app, install Clerk's agent skills, start the app.
Checklist
Looks for another auth provider before init and stops for approval
It inspects dependencies, routes, middleware, sessions and user records, never env files.
Files · Existing auth check
Skips init when Clerk is already in the project
A signed-out init could create another application and replace your keys.
Files · Existing Clerk project guard
auth login, apps list, link --app and env pull for development keys
You run the login. Claude shows app names and IDs and never picks one for you.
Runs code · Use an existing app
Detects framework and package manager, installs the SDK, configures auth
Command: npx -y clerk@latest init. Add --no-skills to skip the global skills install.
Try: “Add Clerk auth to my Next.js app”
Runs code · clerk init
Creates a new app in a subdirectory with --framework and --pm
It can create Next.js, React Router, Astro, Nuxt, TanStack Start, React, Vue, JavaScript/Vite and Expo apps.
Runs code · Empty directory scaffold
Writes temporary keys you can claim later by signing in
Works for Next.js, React Router, Astro, Nuxt and TanStack Start.
Runs code · Accountless dev keys
Follows the matching docs quickstart when init is incomplete
SKILL.md links 14 quickstarts, from Next.js to Android and Chrome extension.
Network · Quickstart fallback
Adds sign-in, sign-up and user buttons to your layout
Next.js server components wrap Show in Suspense.
Write · Auth controls
Verifies the setup and fixes what it reports
Runs code · clerk doctor
If components.json exists, adds @clerk/ui and applies the shadcn theme
Runs code · shadcn/ui theme
Claim the app, review settings, production deploy, optional Organizations
Organizations are offered, and enabled with `clerk enable orgs` only if you say yes.
Runs code · After-setup steps

From the official docs

Permissions

High risk

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It runs a CLI that rewrites your project
`npx -y clerk@latest init` installs the SDK and configures the provider, middleware, auth routes and environment. The -y flag skips npx's install prompt and @latest takes whatever is newest. Run it on a git branch and read the diff. github.com
Init writes keys and installs skills globally
Signed out, init provisions a claimable app and writes temporary development keys to your env file. It also installs Clerk's agent skills globally unless you pass --no-skills. github.com
Production setup touches live infrastructure
`clerk deploy --mode agent --domain <domain>` creates the production instance. Claude may then run the report's hostSetup command to copy keys to Vercel, but only after you confirm the Vercel project. SKILL.md warns that a plain `env pull` with production keys overwrites your local development keys. github.com
It can create test users and change settings
`clerk users create` makes a test user with a generated password, only for a new accountless app. For an existing app SKILL.md says to ask first. `clerk config patch` and `clerk enable orgs` change instance settings. github.com
It must not replace your current login system
If another auth provider exists, SKILL.md says to stop and get approval for a migration plan. It also says not to read or print env files. github.com
The Clerk plugin also adds an MCP server
The plugin bundles .mcp.json, which registers the hosted Clerk MCP server at mcp.clerk.com/mcp. plugin.json lists no hooks. The skills CLI and folder routes do not add it. github.com

Technical details

Turning on read-only	There is no read-only switch. Setup edits your project; the checklist asks you to say yes before it starts.
Talks to	clerk.com. dashboard.clerk.com
Sign-in and keys	SKILL.md has you run `npx -y clerk@latest auth login` in your own terminal to claim an app. Accountless setup writes temporary development keys to the detected env file.
Scopes	Runs npx -y clerk@latest commands in your project Installs the Clerk SDK and edits provider, middleware, auth routes and env files Can create a Clerk production instance and set up your hosting environment

Questions

What does the clerk-setup skill do?

It makes Claude add Clerk authentication to a project with the Clerk CLI. It can set up an existing app, scaffold a new one in an empty folder, or link an existing Clerk application. It then verifies the setup and can walk through production deploy.

How do I install clerk-setup?

Use the install box above. The Clerk plugin installs all 20 skills plus the Clerk MCP server. npx skills add clerk/skills installs the skills alone.

Do I need a Clerk account?

Not to start. The compatibility note says the CLI can provision temporary development keys on supported frameworks without an account. You claim the app later by signing in. Frameworks without that support need real API keys.

What Node.js version does it need?

Node.js 20.9.0 or later for current Clerk SDKs. Core 2 projects need 18.17.0 or later, per SKILL.md.

Will it overwrite my existing auth?

It is told not to. If another provider exists, it stops and asks for approval of a migration plan. If Clerk is already installed, it skips init so it cannot create a second app or replace your keys.

Is it safe?

It runs a CLI that edits your project, writes env keys, installs agent skills globally and can create a production instance. It asks for your yes first. Our advice: run it on a git branch with a clean working tree and read the diff.

clerk-setup vs the clerk router skill?

The repo's clerk skill is a router that sends you to the right skill. clerk-setup is the one that installs Clerk into a project. The README says to start with the router.

Does it work in the Claude app?

The README documents Claude Code, Codex, Cursor, GitHub Copilot CLI and the skills CLI. It documents no Claude app upload route, so use one of those.

Is it an official Clerk skill?

It is in Clerk's own repo, and the repo's marketplace.json describes the plugin as "Official Clerk skills for AI coding agents".

Information

updated Nov 2, 2026

Repository: clerk/skills
Folder: skills/clerk-setup

clerk/skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 5

clerk/skills README · github.com
clerk/skills marketplace.json · github.com
clerk plugin.json · github.com
clerk/skills .mcp.json · github.com
clerk-setup SKILL.md · github.com