360 Secure SkillHub
360 安全技能中心

Riveter

该 Skill 通过 OOMOL 的 oo CLI 调用 Riveter 连接器，凭据由服务端注入，用户不直接处理令牌。提供 get_account（获取账户与 API key 信息）和 scrape（抓取公开网页并返回提取文本）两个动作；执行前先查询动作 Schema，再以 JSON 载荷运行，并附带认证、连接与计费失败的排查步骤。

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

安装技能

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

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

Riveter

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

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

oo connector run "riveter" --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_account — Retrieve the Riveter account and API key details for the connected API key.
  • scrape — Scrape a public webpage with Riveter and return extracted text content.

Safety

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

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

Resources