360 Secure SkillHub
360 安全技能中心

Dealroom

通过 oo CLI 调用 OOMOL 的 dealroom 连接器，提供 search_companies、search_investors、search_transactions 三个只读搜索动作；使用时先查询动作 schema，再以 JSON 载荷执行并返回结构化结果。凭证由 OOMOL 服务端注入，首次使用需安装 oo CLI、登录并连接 Dealroom。

oomol
oomol
热度 25.70
最近更新 2026-09-15 12:59:41
分类：搜索依赖：代码执行 / 第三方 API应用场景：研究 / 市场分析

安装技能

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

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

Dealroom

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

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

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

  • search_companies — Search Dealroom companies with documented keyword, boolean filter, projection, sorting, and pagination options.
  • search_investors — Search Dealroom investment institutions with documented keyword, boolean filter, projection, sorting, and pagination options.
  • search_transactions — Search Dealroom transactions and return their documented funding and round data without inferring seller or exit-party roles.

Safety

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

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

Resources