360 Secure SkillHub
360 安全技能中心

Kadoa

该 Skill 使用 oo CLI 调用 Kadoa 连接器，列出和查看工作流及其执行状态，分页读取最新或指定运行的提取记录，并将匹配记录导出为临时下载链接。凭据由 OOMOL 服务端注入，首次使用需安装 CLI、登录并连接 Kadoa；当前动作均为读取。

oomol
oomol
热度 33.07
最近更新 2026-09-15 12:33:47
分类：数据依赖：代码执行 / 第三方 API应用场景：数据处理 / 工作流

安装技能

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

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

Kadoa

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

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

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

  • export_workflow_data — Materialize all matching Kadoa workflow records and return a temporary signed download URL.
  • get_workflow — Get the current configuration and execution status of a Kadoa workflow.
  • get_workflow_data — Retrieve a bounded JSON page of extracted records from the latest or a specific Kadoa workflow run.
  • list_workflows — List Kadoa workflows with pagination and optional lifecycle, execution, and scheduling filters.

Safety

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

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

Resources