360 Secure SkillHub
360 安全技能中心

Breeze

该 Skill 通过 OOMOL 的 oo CLI 调用 breeze 连接器，读取 Breeze 中的人员记录、资料字段与标签列表；凭证由 OOMOL 服务端注入，用户无需处理原始 token。所列五个动作均为只读，使用前需自行安装 oo CLI 并完成登录与连接。

oomol
oomol
热度 51.61
最近更新 2026-09-16 15:47:16
分类：数据依赖：代码执行 / 第三方 API应用场景：CRM

安装技能

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

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

Breeze

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

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

oo connector run "breeze" --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_person — Get one Breeze person by Breeze person ID.
  • list_people — List people from Breeze with optional details, pagination, and filter_json criteria.
  • list_profile_fields — List Breeze profile sections and fields used to construct Breeze people filters.
  • list_tag_folders — List Breeze tag folders.
  • list_tags — List Breeze tags, optionally narrowed to one Breeze tag folder.

Safety

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

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

Resources