clerk
Clerk Backend API for identity. Use when user mentions "Clerk", "Clerk.com", "user lookup", "ban user", "organization membership", "invitation", or asks about user/org administration.
What this skill does
## Troubleshooting
If requests fail, run `zero doctor check-connector --env-name CLERK_TOKEN` or `zero doctor check-connector --url https://api.clerk.com/v1/users/count --method GET`
## Authentication
All requests require a Bearer token. Use `sk_test_*` for sandbox/dev and `sk_live_*` for production:
```
Authorization: Bearer $CLERK_TOKEN
```
Get the key from Clerk Dashboard → API Keys → Secret keys.
## Users
### Count Users
```bash
curl -s "https://api.clerk.com/v1/users/count" --header "Authorization: Bearer $CLERK_TOKEN"
```
### List Users
Supports `limit` (max 500), `offset`, `email_address`, `phone_number`, `username`, `user_id`, `external_id`, `organization_id`, `query`, `order_by`:
```bash
curl -s "https://api.clerk.com/v1/users?limit=100&order_by=-created_at" --header "Authorization: Bearer $CLERK_TOKEN"
```
### Find User by Email
Returns an array — Clerk allows multiple users per email if confirmed across instances. Replace `<email>` with the actual email:
```bash
curl -s "https://api.clerk.com/v1/users?email_address=<email>" --header "Authorization: Bearer $CLERK_TOKEN"
```
### Get User by ID
Replace `<user-id>` with the actual Clerk user ID (starts with `user_`):
```bash
curl -s "https://api.clerk.com/v1/users/<user-id>" --header "Authorization: Bearer $CLERK_TOKEN"
```
### Update User
Write to `/tmp/clerk_request.json`:
```json
{
"first_name": "Jane",
"last_name": "Doe",
"public_metadata": { "plan": "pro" }
}
```
Replace `<user-id>` with the actual user ID:
```bash
curl -s -X PATCH "https://api.clerk.com/v1/users/<user-id>" --header "Authorization: Bearer $CLERK_TOKEN" --header "Content-Type: application/json" -d @/tmp/clerk_request.json
```
### Ban / Unban User
Replace `<user-id>` with the actual user ID:
```bash
curl -s -X POST "https://api.clerk.com/v1/users/<user-id>/ban" --header "Authorization: Bearer $CLERK_TOKEN"
curl -s -X POST "https://api.clerk.com/v1/users/<user-id>/unban" --header "Authorization: Bearer $CLERK_TOKEN"
```
### Lock / Unlock User
Replace `<user-id>` with the actual user ID:
```bash
curl -s -X POST "https://api.clerk.com/v1/users/<user-id>/lock" --header "Authorization: Bearer $CLERK_TOKEN"
curl -s -X POST "https://api.clerk.com/v1/users/<user-id>/unlock" --header "Authorization: Bearer $CLERK_TOKEN"
```
### Delete User
Hard-deletes the user and all sessions. Replace `<user-id>` with the actual user ID:
```bash
curl -s -X DELETE "https://api.clerk.com/v1/users/<user-id>" --header "Authorization: Bearer $CLERK_TOKEN"
```
### List User's Organization Memberships
Replace `<user-id>` with the actual user ID:
```bash
curl -s "https://api.clerk.com/v1/users/<user-id>/organization_memberships" --header "Authorization: Bearer $CLERK_TOKEN"
```
## Organizations
### List Organizations
Supports `limit` (max 500), `offset`, `query`, `order_by`:
```bash
curl -s "https://api.clerk.com/v1/organizations?limit=100&order_by=-created_at" --header "Authorization: Bearer $CLERK_TOKEN"
```
### Get Organization by ID
Replace `<organization-id>` with the actual org ID (starts with `org_`):
```bash
curl -s "https://api.clerk.com/v1/organizations/<organization-id>" --header "Authorization: Bearer $CLERK_TOKEN"
```
### List Organization Memberships
Replace `<organization-id>` with the actual org ID:
```bash
curl -s "https://api.clerk.com/v1/organizations/<organization-id>/memberships?limit=100" --header "Authorization: Bearer $CLERK_TOKEN"
```
### Create Organization Membership
Write to `/tmp/clerk_request.json`:
```json
{
"user_id": "user_xxx",
"role": "org:member"
}
```
Replace `<organization-id>` with the actual org ID:
```bash
curl -s -X POST "https://api.clerk.com/v1/organizations/<organization-id>/memberships" --header "Authorization: Bearer $CLERK_TOKEN" --header "Content-Type: application/json" -d @/tmp/clerk_request.json
```
### Remove Organization Member
Replace `<organization-id>` and `<user-id>` with the actual IDs:
```bash
curl -s -X DELETE "https://api.clerk.com/v1/organizations/<organization-id>/memberships/<user-id>" --header "Authorization: Bearer $CLERK_TOKEN"
```
## Invitations
### List Pending Invitations
```bash
curl -s "https://api.clerk.com/v1/invitations?status=pending" --header "Authorization: Bearer $CLERK_TOKEN"
```
### Create Invitation
Write to `/tmp/clerk_request.json`:
```json
{
"email_address": "[email protected]",
"redirect_url": "https://app.example.com/accept",
"public_metadata": { "source": "manual" }
}
```
```bash
curl -s -X POST "https://api.clerk.com/v1/invitations" --header "Authorization: Bearer $CLERK_TOKEN" --header "Content-Type: application/json" -d @/tmp/clerk_request.json
```
### Revoke Invitation
Replace `<invitation-id>` with the actual invitation ID:
```bash
curl -s -X POST "https://api.clerk.com/v1/invitations/<invitation-id>/revoke" --header "Authorization: Bearer $CLERK_TOKEN"
```
## Sessions
### List Sessions
Filter by `user_id`, `client_id`, or `status`:
```bash
curl -s "https://api.clerk.com/v1/sessions?status=active&limit=100" --header "Authorization: Bearer $CLERK_TOKEN"
```
### Revoke Session
Replace `<session-id>` with the actual session ID:
```bash
curl -s -X POST "https://api.clerk.com/v1/sessions/<session-id>/revoke" --header "Authorization: Bearer $CLERK_TOKEN"
```
## Guidelines
1. **Test vs Live**: Secret keys are environment-scoped. `sk_test_*` only works on the development instance; `sk_live_*` only works on production. Confirm the environment before destructive operations.
2. **Pagination**: Use `limit` (max 500) and `offset`. Total count is in the `total_count` field of the response wrapper.
3. **Destructive operations** (delete, ban, lock, revoke) are irreversible or hard to reverse — verify the target user/org ID before running.
4. **Rate limits**: Backend API allows 1,000 requests/10 seconds per instance. Implement exponential backoff on HTTP 429.
5. **User metadata**: Use `public_metadata` for data visible to the user, `private_metadata` for backend-only data, `unsafe_metadata` for end-user-mutable data.
## API Reference
- Documentation: https://clerk.com/docs/reference/backend-api
- OpenAPI spec: https://github.com/clerk/openapi-specs
- Dashboard: https://dashboard.clerk.com
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.