Install
npx skills add clerk/skillsWho it's for
Use this skill set when you want a coding Agent to handle Clerk authentication more smoothly — especially adding Clerk to a new project or any framework, or checking users, organizations, apps, environment keys, and deploys. The skills follow the Agent Skills format and target developers who need Clerk in a codebase and want the Agent to pick the right skill before changing anything. Official text marks /clerk as the router and says always start there; do not name a child skill up front. Before you start, you must be able to open Clerk Dashboard and get keys you can write into an environment file; otherwise setup and checks stop on missing keys.
First try in 3 minutes
Use only the install command from the official repository:
npx skills add clerk/skills
After install, prepare keys first; do not pad with placeholders. Open Clerk Dashboard, copy the publishable key and the secret key, and write them into the project .env. The key names must be NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY. Before writing, have the Agent only repeat those two key names and the target file; allow the file change only after you confirm.
For the first task, pick a reversible check, not a framework change. In a client that already loaded the skills, type /clerk, say you want a deploy check or to verify environment keys, and let the router take you to clerk-cli. Before any command runs, require the Agent to say it will call a CLI check and will not create users or change organizations. Run only after you confirm.
Success signal: the Agent goes from /clerk into clerk-cli and returns environment-key or deploy-check results, instead of missing-skill or missing-key errors. If you use Codex, official text has a separate marketplace add command; after adding, restart, open /plugins, choose Clerk Skills, install and enable clerk-skills, then start a new thread. That is a Codex-only sequence; do not treat it as the default install.
Use cases
Case 1: Add Clerk to a new project or any framework. Official skill clerk-setup is responsible for adding Clerk to any framework, including new projects and framework init. The path is /clerk first, state the current framework and “only add Clerk setup”, then let the router land on clerk-setup. This kind of task changes project files; the Agent must list the files it will change, and you confirm before any write. The page does not give a concrete framework list or step-by-step patches; framework details follow the skill notes after install.
Case 2: Read-only operations checks via CLI. clerk-cli covers users, organizations, apps, environment keys, and deploy checks. After keys are in .env, use it to see whether an existing app can deploy, whether keys are complete, or to view users and organizations read-only. Again start with /clerk, then enter clerk-cli. The page does not list concrete CLI subcommands, so do not invent command names; what you can confirm are the check categories above. Output format follows the actual run.
Boundaries
Do not start setup without Dashboard keys. The environment file uses only the two key names official text wrote; do not rename them to undocumented variables. Default install is npx skills add clerk/skills; marketplace install applies only to Codex and must enable clerk-skills in the official order. Always start from /clerk; the page does not describe other entries as a way to skip the router. Official text does not list a complete client roster; do not infer exclusive support from the Codex example, and do not infer language coverage from page examples. Do not invent undocumented skill directories, marketplace commands, or key samples. Repository page:
https://github.com/clerk/skills
Dashboard:
https://dashboard.clerk.com/