360 Secure SkillHub
360 安全技能中心

Cubox

该 Skill 通过 OOMOL 的 oo CLI 调用 cubox 连接器，目前仅提供 save_url（[write]）动作，可把网页保存到 Cubox 以便排队解析和快照处理。使用前提是已安装 oo CLI、登录 OOMOL 账号并连接 Cubox 服务，凭据由服务端注入；运行时先查询动作 schema，再以 JSON 载荷执行。

oomol
oomol
热度 22.12
最近更新 2026-09-15 13:44:06
分类：知识依赖：代码执行 / 第三方 API应用场景：笔记整理

安装技能

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

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

Cubox

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

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

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

  • save_url — Save a web page to Cubox for queued parsing and snapshot processing. [write]

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Cubox 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 — Cubox is not connected, or the connection expired or lacks a scope. Connect once (auth type: custom credential) at:

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

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

Resources