360 Secure SkillHub
360 安全技能中心

Clerk

核心功能：通过oo CLI调用Clerk连接器，实现用户增删改查、封禁/解锁/锁定等状态管理，支持带过滤的用户统计与列表查询。典型场景：用户账号批量管理、违规用户处理、用户信息更新等。输入为符合对应操作schema的JSON数据，通过bash命令执行；输出含操作结果及执行ID的JSON结构。无需手动处理凭证，OOMOL后台注入；首次失败需完成CLI安装、登录及Clerk连接，写操作和破坏性操作需用户确认。

oomol
oomol
热度 53.90
最近更新 2026-09-20 11:28:40
分类：自动化依赖：代码执行应用场景：自动化脚本 / 数据处理 / CRM

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-clerk
Metadata
name
oo-clerk
description
Clerk (clerk.com). Use this skill for ANY Clerk request — reading, creating, updating, and deleting data. Whenever a task involves Clerk, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Clerk","author":"OOMOL","version":"1.0.5","services":["clerk"],"icon":"https://static.oomol.com/logo/third-party/clerk.svg"}

Clerk

Operate Clerk through your OOMOL-connected account. This skill calls the clerk connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Clerk. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "clerk" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "clerk" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • ban_user — Ban a Clerk user. [destructive]
  • count_users — Count Clerk users with optional filters.
  • create_user — Create a Clerk user. [write]
  • delete_user — Delete a Clerk user. [destructive]
  • get_user — Retrieve a Clerk user by ID.
  • list_users — List Clerk users with optional filtering and pagination.
  • lock_user — Lock a Clerk user. [write]
  • unban_user — Unban a Clerk user. [write]
  • unlock_user — Unlock a Clerk user. [write]
  • update_user — Update a Clerk user. [write]
  • update_user_metadata — Deep merge metadata for a Clerk user. [write]

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Clerk state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — Clerk is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=clerk

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources