clerk-backend-api

Execute authenticated Clerk Backend REST API calls for user and organization management.

1|Updated May 1, 2026
One-click install
npx skills add https://github.com/Joshkovu/ghost-ai --skill clerk-backend-api-joshkovu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk-backend-api
Source: https://github.com/Joshkovu/ghost-ai/tree/main/.agents/skills/clerk-backend-api
Command: npx skills add https://github.com/Joshkovu/ghost-ai --skill clerk-backend-api-joshkovu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, curl, python3, bash.

What problem does it solve?

It helps you discover Clerk Backend API endpoints and safely execute authenticated requests to manage users and organizations without guessing paths, schemas, or payload formats.

Core Features & Use Cases

  • Tag browsing: List available API tags and drill into endpoint sets by tag.
  • Endpoint inspection: View full endpoint definitions and referenced component schemas before running requests.
  • Authenticated execution: Execute Clerk Backend API calls with required Bearer authentication and enforced safety checks for writes and deletes.
  • Common admin workflows: List users (with date filters), create organizations, invite members, update user metadata, and perform destructive deletes with explicit confirmation.

Quick Start

Run clerk-backend-api GET /users to fetch users from Clerk, using your CLERK_SECRET_KEY for Bearer authentication.

Frequently Asked Questions about clerk-backend-api

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

FAQPage Schema
How do I call Clerk Backend API endpoints to manage users and organizations?

You can execute authenticated Clerk Backend API endpoints for user and organization management by providing your CLERK_SECRET_KEY for Bearer authentication, enabling actions like listing users, creating organizations, and sending invitations.

How do I inspect Clerk Backend API schemas before executing a write request?

You can browse available API tags and drill into endpoint sets to view full endpoint definitions and referenced component schemas, ensuring you have the correct payload format before running authenticated requests.

Do I need a CLERK_SECRET_KEY to fetch users from the Clerk Backend API?

Yes, the CLERK_SECRET_KEY is required for every Clerk Backend API call to enforce Bearer authentication, including read operations like fetching users with date filters.

What safety checks are enforced for destructive Clerk API operations like deleting users?

Write and delete operations require mandatory pre-checks including CLERK_BAPI_SCOPES validation and explicit confirmation before executing destructive Clerk Backend API requests.

Can I update user metadata directly through the Clerk Backend API?

Yes, you can update user metadata by executing the appropriate Clerk Backend API endpoint with your CLERK_SECRET_KEY, with mandatory pre-checks enforced for the write operation.

Does this approach require specific runtime environments to execute Clerk API requests?

Executing Clerk API requests via direct curl requires a compatible environment with dependencies like node, python3, or bash installed to handle JSON response parsing and key-field summarization.