clerk-backend-api

To safely execute Clerk Backend API calls, this Skill enforces CLERK_SECRET_KEY presence and scope verification, issuing warnings before any mutating POST, PATCH, PUT, or DELETE requests to prevent accidental data loss.

Yes, you can update Clerk user metadata through the Backend API. This Skill provides ready-to-run templates and guidance for correctly applying public, private, and unsafe metadata types to user profiles.

You can list users created in the last seven days by asking this Skill to execute the list users command. It generates ready-to-run curl templates for common tasks like listing users and creating organizations.

To make mutating Clerk Backend API requests, you need the CLERK_SECRET_KEY environment variable for authentication. The Skill also respects CLERK_BAPI_SCOPES to enforce safety checks before any write operations.

Yes, the Clerk Backend API has production and development rate limits. This Skill provides information on these limits and suggests mitigation strategies to help you avoid hitting them during user management operations.

You can browse Clerk OpenAPI specifications by asking this Skill to explore tags and endpoints. It allows spec-driven browsing to help you find the correct backend API endpoints for your organization and user management tasks.