360 Secure SkillHub
360 安全技能中心

Lucid SCIM

该 Skill 借助 oo CLI 调用 OOMOL 托管的 lucid_scim 连接器，凭证由服务端注入，用户无需处理原始令牌。提供 get_user、get_group、list_users、list_groups、get_service_provider_config 五个只读动作，按动作 Schema 以 JSON 参数查询 Lucid SCIM 用户、组及服务提供方配置，返回结构化结…

oomol
oomol
热度 45.76
最近更新 2026-09-15 12:33:49
分类：搜索依赖：代码执行 / 第三方 API应用场景：API 集成

安装技能

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

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

Lucid SCIM

Operate Lucid SCIM through your OOMOL-connected account. This skill calls the lucid_scim 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 Lucid SCIM. 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 "lucid_scim" --action "<action_name>"

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

oo connector run "lucid_scim" --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

  • get_group — Get one Lucid SCIM org group or team by ID.
  • get_service_provider_config — Get the Lucid SCIM service provider configuration for the connected account.
  • get_user — Get one Lucid SCIM user by ID.
  • list_groups — List Lucid SCIM org groups or teams with optional SCIM filter, pagination, and attributes.
  • list_users — List Lucid SCIM users with optional SCIM filter, pagination, and attributes.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Lucid SCIM 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 — Lucid SCIM 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=lucid_scim

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

Resources