REPO PACKAGE
clerk skills
COMMUNITY21skills
2ready to use
LABSCO SUMMARY
Twelve of the 22 are platform- or framework-specific pattern guides: one each for Next.js, React, React Router, Vue, Nuxt, Astro, TanStack Start, Chrome extensions, Android (Kotlin/Compose), and Swift (iOS), plus two separate Expo skills. The other ten split into five core skills (a router, CLI operations, custom UI, the backend REST API, and generic framework setup), four feature skills (organizations, billing, webhooks, and Playwright/Cypress testing), and one maintenance skill, audit-clerk-skill, that checks the bundled clerk-cli skill against Clerk's actual CLI source and proposes fixes when it drifts.
This is for a team already on Clerk who wants an agent that knows the current SDK per framework rather than generic auth advice. If you have not set up a Clerk project yet, only the router and the audit tool will do anything before you do — every framework, feature, and mobile skill assumes a live Clerk account is already configured, with a publishable key and secret key in .env.
READ THE FULL ANALYSIS
Two of the 22 are missing from the README's own map. Clerk's file-structure tree documents four folders — core, frameworks, features, mobile — and names 20 of the 22 by path; the audit tool and a plain clerk-expo skill (distinct from clerk-expo-patterns) do not appear in that tree or in any of the README's own skill tables, even though both are live in the repository today.
One skill has no description in our capture. clerk-expo-patterns is the one the README's own quickstart table points to for Expo apps, but our database has no frontmatter description for it, so we cannot say more here than its name and framework target.
Checked 19 September 2026 from the repository README and its 22 currently live skills.
ALSO IN THIS PACKAGE
PLUGINS
4 itemsPLUGIN
core
Core Clerk skills: router, CLI operations, setup, custom UI, and API references
PLUGIN
frameworks
Framework-specific Clerk integration patterns: middleware, hooks, SSR, composables, and advanced usage
PLUGIN
features
Clerk feature skills: organizations, billing, webhooks, and testing
PLUGIN
mobile
Mobile Clerk auth: Swift/iOS, Android/Kotlin, and Expo/React Native patterns
WHAT'S INSIDE
21 showing · 21 totalReady to use
Nothing else to set up — install it and go.
21 of 21
SETUP
Showing all 21 skills
audit-clerk-skill
Compares the bundled clerk-cli skill's documentation against the real Clerk CLI source code and lists every command, flag, or behavior that is missing, outdated, or overstated.
clerk
Figures out which version of the Clerk SDK a project is on, then points you to the specific Clerk skill for your framework or feature.
clerk-android
Adds Clerk sign-in to a native Android app, using either Clerk's prebuilt auth screens or a custom flow built against the API directly.
clerk-astro-patterns
Astro builds some pages ahead of time and some on request, and only the second kind can tell who is signed in; this is how to get Clerk working across both.
clerk-backend-api
Browses and calls any Clerk Backend API endpoint directly, from listing users to inviting an organization member, without you having to look up the API spec by hand.
clerk-billing
Sets up paid subscriptions on top of Clerk's user accounts, so the same system that knows who someone is also knows what they have paid for.
clerk-chrome-extension-patterns
Adds Clerk sign-in to a Chrome extension's popup, side panel, background service worker, or content scripts, working around the auth methods each surface can't support.
clerk-cli
Runs the `clerk` command-line tool for everyday account and instance work — logging in, managing users and organizations, testing webhooks locally, and calling any Clerk API endpoint.
clerk-custom-ui
Builds your own sign-in and sign-up screens with Clerk's hooks, or restyles Clerk's pre-built ones with themes, colors, and a custom logo.
clerk-expo
Adds Clerk sign-in to an Expo or React Native app, choosing between prebuilt native auth screens and a custom flow, and verifying the build actually works.
clerk-nextjs-patterns
The harder half of Clerk in Next.js: your code runs in two places, the server and the browser, and each has to ask who is signed in a different way.
clerk-nuxt-patterns
Installing the Clerk module into a Nuxt app wires up most of the plumbing by itself; this covers the bit you still write yourself.
clerk-orgs
Makes your users belong to a company or team rather than only to themselves, with members, roles, invitations and each team's own data.
clerk-react-patterns
Adding sign-in to a plain React app built with Vite or Create React App, where everything happens in the browser and there is no server side to check on.
clerk-react-router-patterns
Wires Clerk into a React Router v7 or v8 app's middleware and loader pipeline, and works around a specific SSR bug that only shows up in v8's dev server.
clerk-setup
Gets sign-up and login working in an app that has none: it detects which framework you are using, installs Clerk's kit, and provisions the Clerk side from the command line without a dashboard visit.
clerk-swift
Adds Clerk sign-in to a native iOS Swift app, using either Clerk's prebuilt auth screens or a custom flow built against the API directly.
clerk-tanstack-patterns
The worked examples for putting Clerk's logins into a TanStack Start app: keeping signed-out visitors off a page, reading who is signed in from server code, and plugging Clerk into the server so both actually work.
clerk-testing
Automated browser tests normally get stuck at the login screen; this wires them up to sign in as a real Clerk user first, in either Playwright or Cypress.
clerk-vue-patterns
Clerk in a plain Vue 3 app, in copy-paste form: showing who is signed in, wiring the sign-in and sign-out buttons, and letting someone switch between the teams they belong to.
clerk-webhooks
Clerk tells your own server the moment someone signs up, edits their profile or joins a team; this writes the code that receives those messages and proves each one really came from Clerk.
No skill in this package matches that.
HOW TO GET IT
WHOLE PACKAGEInstall the whole package (21 skills)
npx skills add clerk/skillsSINGLE SKILLOr install a single skill
npx skills add clerk/skills --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.
PLUGIN MARKETPLACEAdd the marketplace, then install the plugins you want
/plugin marketplace add clerk/skills/plugin install core@clerk-skills/plugin install frameworks@clerk-skills/plugin install features@clerk-skillsTyped inside the agent's own prompt, not in a terminal. The marketplace lists 4 plugins; three are shown. Every one installs the same way, with its own name before @clerk-skills.