clerk-cli

Authenticate and administer Clerk resources via the official CLI.

Updated May 30, 2026
One-click install
npx skills add https://github.com/Athone88/Anima --skill clerk-cli-athone88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk-cli
Source: https://github.com/Athone88/Anima/tree/main/.agents/skills/clerk-cli
Command: npx skills add https://github.com/Athone88/Anima --skill clerk-cli-athone88

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The clerk-cli skill helps you manage Clerk authentication and project resources reliably without hand-crafted HTTP calls, reducing time spent debugging auth, key targeting, and endpoint discovery.

Core Features & Use Cases

  • Operate Clerk via the official CLI: run clerk commands for authentication, linking, doctor checks, environment key pulls, and instance/app targeting.
  • Perform safe API operations: use clerk api and prefer clerk config/clerk env pull, including dry-runs for mutations to reduce accidental destructive changes.
  • Work effectively in agent mode: follow the CLI’s agent-mode rules for non-interactive behavior, including handling the host/sandbox warning and using --json for structured outputs.

Quick Start

Ask the agent: Pull the current Clerk dev environment keys into the project’s env file and show what changed.

Frequently Asked Questions about clerk-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Clerk authentication and users without making manual API calls?

You can manage Clerk authentication by running the official clerk CLI through an agent, which automatically handles API selection, key resolution, and instance targeting to list users or update organizations without hand-crafted HTTP requests.

What is the best way to pull Clerk environment keys into a local project file?

Pulling Clerk environment keys is best done using the `clerk env pull` command, which retrieves current dev environment keys directly into your project's env file while running in a non-interactive agent mode.

How do I safely execute Clerk Backend or Platform API mutations?

Safely execute Clerk API mutations by using the `clerk api` command with the `--dry-run` flag, allowing you to preview changes and reduce accidental destructive actions before applying any updates to users or organizations.

Can I run Clerk CLI commands non-interactively within an automated agent workflow?

Yes, the Clerk CLI supports agent mode by using deterministic options like `--json` for structured outputs, `--dry-run` for safe executions, and explicit targeting flags to avoid interactive prompts during automation.

Why should I run `clerk doctor --json` before executing other Clerk commands?

Running `clerk doctor --json` first is required to verify your environment setup and diagnose configuration issues, ensuring that subsequent CLI commands resolve API keys and target the correct app or instance reliably.

Does the Clerk CLI require any specific dependencies to administer instance config?

Administering Clerk instance config requires a pinned clerk binary to ensure consistent command execution, but no external dependencies are needed as the CLI handles key resolution and endpoint discovery internally.