This skill covers Clerk sign-in, organizations, roles and billing on Next.js App Router with Clerk Core 3. It decides what Clerk’s API guidance cannot: where a session is verified, what a workspace is, where billing ends and authorization begins, and which dashboard settings change what the code may do.
It sends the agent to Clerk’s own skills for API details, then overrides their defaults where they conflict with its thirteen numbered choices. It lists setup steps in order, a record to keep of each dashboard setting, and a gotchas file for sign-in that does nothing or lands in the wrong place.
What You Get
- Thirteen numbered choices for sessions, workspaces, sign-in redirects, organizations, billing and the content security policy
- An ordered setup list: application, workspace model, second role, test mode, billing, legal consent, production instance
- Reference files for sessions, organizations and billing, CSP and variables, the authenticated browser test mile, MCP OAuth and gotchas
- A list of dated read-backs to keep for every dashboard setting that code cannot see
- A receipts file that gives the case behind each rule
Common Use Cases
- Adding sign-in and organizations to a new Next.js product
- Setting up Clerk Billing with a plans file applied through the Clerk CLI
- Moving a Clerk development instance to production at go-live
- Debugging sign-in that does nothing, or lands on the wrong page
What Makes It Unique
Clerk ships its own skills for its API. This skill covers the decisions those skills leave to you and states that it wins where Clerk’s quickstart contradicts it. It names the settings that fail silently, such as a lapsed subscription removing a permission, a development-only refusal, or a cloned production instance dropping API-only settings. Each rule links to a dated case.
Under The Hood
The skill is instructions and reference markdown with no scripts of its own. Following it, the agent runs shell commands: it installs Clerk’s skills with the skills CLI from GitHub, runs the Clerk CLI to patch and pull instance configuration (with a dry run first), and runs the app’s tests. It calls Clerk’s Backend API with the development secret key to change organization settings, roles and test mode and to read them back, and fetches the instance’s public environment settings over the network. It also edits files in the product: proxy and layout code, billing files and integration notes.