clerk-clilisted

Operate Clerk from a coding-agent terminal with the official clerk CLI and bundled Backend API helpers. Use when the agent needs to inspect or manage Clerk applications, users, organizations, memberships, invitations, sessions, impersonation, JWT templates, instance configuration, allowlists, blocklists, domains, OAuth applications, SAML connections, webhooks, or Clerk tokens; invoke clerk-cli or the Clerk CLI; diagnose Clerk authentication or project linking; call the Clerk Backend API; or translate a legacy Clerk MCP management workflow to shell commands. Do not use for application runtime integration through Clerk SDKs, frontend sign-in flows, continuous monitoring, or Clerk MCP server configuration.
arthjean/skills · ★ 3 · AI & Automation · score 66

Install: claude install-skill arthjean/skills

# Clerk CLI Operate Clerk through `bunx clerk@latest --mode agent` and the bundled Bash helpers. Keep the working directory in the user's project so Clerk can resolve its linked application and local environment files. ## Operating contract 1. Set the absolute directory containing this `SKILL.md` as `CLERK_SKILL_DIR`. In a standard user installation: ```bash CLERK_SKILL_DIR="${CLERK_SKILL_DIR:-$HOME/.agents/skills/clerk-cli}" ``` 2. Do not `cd` into the skill directory. Invoke helpers with `bash "$CLERK_SKILL_DIR/scripts/<script>.sh"` from the target project. 3. Use `bunx clerk@latest --mode agent`. Do not install Clerk CLI globally and do not use npm, npx, pnpm, or yarn. 4. Prefer `CLERK_SECRET_KEY` in the environment for Backend API operations. Never place a literal key in `--secret-key`, command output, committed files, or generated artifacts. 5. Prefer the official CLI. Use bundled helpers for REST gaps, deterministic JSON pipelines, metadata merges, or repeated resource workflows. 6. Keep browser use opt-in. Do not run `clerk auth login`, `clerk open`, `clerk users open`, or an option that opens a URL unless the user explicitly requested browser authentication or navigation. 7. Require explicit intent and an unambiguous application, instance, and resource before any create, update, invitation, impersonation, revocation, deletion, deploy, or secret-producing operation. An exact user request is authorization, so do not add a redundant confirmation. 8. Inspect