Clerk CLI

The clerk binary is a pre-authenticated gateway to Clerk's Backend API and Platform API, plus project-level tooling (auth, linking, env pulls, instance config). When the user asks anything that touches a Clerk resource, reach for clerk first instead of hand-rolling curl.

This skill was installed by clerk init (or clerk skill install) and is pinned to clerk {{CLI_VERSION}}. If clerk --version disagrees, refresh it with clerk skill install (or bunx clerk@{{CLI_VERSION}} skill install). The binary is always the source of truth, so run clerk <command> --help to verify anything this skill claims.

Execution environment (prefer the host, understand the sandbox warning)

Most AI coding agents default to running shell commands in a sandbox where the user's home directory, OS keychain, browser launch, localhost callback binding, or network access may be blocked. The Clerk CLI depends on all of those host capabilities:

• OS credential store: clerk auth login stores the OAuth token in the system keychain. A sandbox without keychain access reports "not logged in" even when the host is authenticated.
• Home-directory Clerk state: saved config, cached metadata, and fallback credentials live under the user's Clerk config/data directories.
• Linked project metadata: resolved from the repo's git remote plus Clerk