360 Secure SkillHub
360 安全技能中心

Táve

该 Skill 通过 OOMOL 的 oo CLI 调用 Táve 连接器，在已连接的账号下执行 get_contact、get_my_studio、list_contacts 三个读取动作，支持分页、隐藏、邮箱与排序筛选；凭据由 OOMOL 服务端注入，用户不接触原始令牌；未列出写入或删除类动作，运行前需先用 schema 获取权威输入结构。

oomol
oomol
热度 50.44
最近更新 2026-09-15 14:03:39
分类：搜索依赖：代码执行 / 第三方 API应用场景：CRM

安装技能

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

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

Táve

Operate Táve through your OOMOL-connected account. This skill calls the tave 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 Táve. 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 "tave" --action "<action_name>"

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

oo connector run "tave" --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_contact — Fetch one Táve contact by its official ULID identifier.
  • get_my_studio — Fetch the current Táve studio profile for the connected API key.
  • list_contacts — List contacts in the current Táve studio with official pagination, hidden, email, and sort filters.

Safety

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

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

Resources