What problem does it solve? Managing Clerk resources (users, organizations, sessions, instance config, env keys) through raw HTTP requests requires manual key resolution, app targeting, and error handling. This Skill teaches an AI agent to drive the pre-authenticated clerk CLI instead, so auth, key resolution, and formatting are handled automatically. ## Core Features & Use Cases - User and organization management: List, create, update, ban, or delete users and manage organizations, memberships, sessions, and invitations via curated commands or clerk api calls. - Instance configuration and env keys: Pull, patch, or replace instance config with dry-run previews, and materialize publishable/secret keys into .env.local with clerk env pull. - Deploy verification and diagnostics: Run clerk doctor --json health checks and verify production deploys with clerk deploy status, including agent-mode sandbox warnings. - Use Case: When a user asks to "list all banned Clerk users in production", the agent runs clerk users list --instance prod --json, saves the output to a file, and queries it with jq instead of flooding the context window. ## Quick Start Ask the agent to run clerk doctor --json to verify the CLI is authenticated and linked, then request any Clerk task such as listing users or pulling environment keys.
