clerk-backend-api

Execute authenticated Clerk Backend REST API requests to manage users, organizations, and invitations by ensuring the presence of CLERK_SECRET_KEY and validating CLERK_BAPI_SCOPES for write or delete operations. The skill applies safe defaults to prevent unauthorized or accidental modifications.

Browse Clerk Backend API endpoints by tag to inspect request and response schemas. The skill allows you to discover endpoint structures and execute authenticated REST API calls to manage Clerk resources like users, organizations, and metadata.

Yes, you can list users, create organizations, invite members, and update user metadata through the Clerk Backend API. The skill supports these common tasks by executing authenticated REST API requests with proper security checks like CLERK_SECRET_KEY validation.

Yes, executing write or delete operations on Clerk Backend API endpoints requires CLERK_BAPI_SCOPES validation. The skill enforces this security check alongside verifying the CLERK_SECRET_KEY presence to ensure safe and authorized API execution.

The skill provides explicit warnings for irreversible delete operations on Clerk resources. It enforces safe defaults and security checks like CLERK_BAPI_SCOPES validation to prevent accidental data loss when managing users or organizations via the REST API.

Yes, you need a CLERK_SECRET_KEY to manage Clerk user metadata. The skill enforces the presence of this key to ensure authenticated and secure REST API execution for all read and write operations on Clerk resources.