clerk-backend-api

Execute authenticated Clerk Backend API workflows for users, organizations, and metadata.

Updated Aug 23, 2026

Search Tags:#authentication #rest #metadata #curl #organizations #clerk #backend api

Ready to run

npx skills add https://github.com/MichaelFrieze/riffatlas --skill clerk-backend-api-michaelfrieze

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clerk-backend-api
Source: https://github.com/MichaelFrieze/riffatlas/tree/main/.agents/skills/clerk-backend-api
Command: npx skills add https://github.com/MichaelFrieze/riffatlas --skill clerk-backend-api-michaelfrieze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you reliably browse Clerk Backend API endpoints and then execute authenticated requests to manage users and organizations without guessing schemas or payload shapes.

Core Features & Use Cases

Endpoint discovery and inspection: Browse available tags and view full request/response schemas for a specific endpoint before running anything.
Fast-path common operations: Quickly list users, create organizations, send organization invitations, update user metadata, and delete users using ready-to-run curl templates.
Safety guardrails for sensitive writes: Enforces mandatory checks for CLERK_SECRET_KEY presence, scope validation for write/delete operations, and irreversible-delete warnings with explicit confirmation.

Quick Start

Use the clerk-backend-api skill to list users signed up in the last 7 days by running a GET /users request with an appropriate created_at filter and Bearer auth using CLERK_SECRET_KEY.

Frequently Asked Questions about clerk-backend-api

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

FAQPage Schema

How do I make authenticated Clerk Backend API calls to manage users?▼

Browse Clerk Backend API endpoint schemas and execute authenticated REST requests to manage users and organizations without guessing payload shapes by leveraging ready-to-run curl templates.

What do I need to perform write or delete operations on the Clerk Backend API?▼

Write and delete operations against the Clerk Backend API require mandatory CLERK_SECRET_KEY presence and CLERK_BAPI_SCOPES validation to authorize sensitive administrative actions like creating organizations.

Can I update public, private, and unsafe user metadata via the Clerk Backend API?▼

Yes, you can update public, private, and unsafe user metadata via the Clerk Backend API by applying provided fast-path templates that execute authenticated REST calls to modify user attributes.

How do I list Clerk users who signed up within a specific date range?▼

List Clerk users who signed up within a specific date range by executing a GET /users request with a created_at filter, Bearer auth, and pagination support via limit and offset parameters.

Are there safety guardrails for irreversible user deletions in the Clerk Backend API?▼

The Clerk Backend API enforces safety guardrails for irreversible user deletions by triggering explicit delete warnings that require explicit confirmation before executing controlled deletion operations.