360 Secure SkillHub
360 安全技能中心

Trent

该 Skill 通过 OOMOL 的 oo CLI 连接 Trent，仅提供 send_chat 动作，用于向 Trent 聊天端点发送一条消息并返回响应内容与线程元数据。写入前需确认载荷；首次使用需安装 CLI、登录并连接服务。

oomol
oomol
热度 43.08
最近更新 2026-09-15 13:06:31
分类：协作依赖：代码执行 / 第三方 API / 读写文件应用场景：工作流 / API 集成

安装技能

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

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

Trent

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

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

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

  • send_chat — Send one message to Trent's chat endpoint and return the assembled response content plus thread metadata. [write]

Safety

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

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

Resources