What problem does it solve? Managing Clerk authentication resources through raw HTTP calls requires manual key handling, endpoint memorization, and error-prone curl commands. This Skill teaches an AI agent to drive the pre-authenticated clerk CLI for user, organization, session, webhook, and instance-config operations with correct auth resolution, agent-mode behavior, and safe mutation previews. ## Core Features & Use Cases - Backend, Platform, and Frontend API access: Use clerk api <path> with automatic key resolution, method detection, --dry-run previews, and endpoint discovery via clerk api ls. - User and org management: List, create, update, ban, and impersonate users; manage organizations, memberships, invitations, sessions, and JWT templates. - Instance configuration and deploys: Pull, patch, and replace instance config, toggle orgs and billing, pull env keys, and verify production deploys with clerk deploy status. - Local webhook testing: Tunnel deliveries to a local handler with clerk webhooks listen and verify signatures offline with clerk webhooks verify. - Use Case: Ask the agent to list all banned users on your production instance; it runs clerk doctor --json first, saves clerk users list --json output to a file, and queries it with jq instead of flooding the conversation. ## Quick Start Ask the agent to run clerk doctor and then list the ten most recently created users on your linked Clerk application.
