360 Secure SkillHub
360 安全技能中心

BetterContact

该 Skill 借助 OOMOL 的 oo CLI 连接器操作 BetterContact：可查询账户余额、按请求 ID 获取线索富集结果，以及提交一条或多条线索进行瀑布式富集。凭据由 OOMOL 服务端注入，用户无需处理令牌。运行前需用 schema 动作确认输入字段，写操作需用户确认。

oomol
oomol
热度 51.80
最近更新 2026-09-15 13:31:21
分类：营销依赖：代码执行 / 第三方 API应用场景：数据处理

安装技能

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

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

BetterContact

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

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

oo connector run "bettercontact" --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_balance — Get BetterContact credits for the connected account email or an optional email override.
  • get_enrichment_result — Get the current BetterContact enrichment result for a submitted request ID.
  • submit_enrichment — Submit one or more leads to BetterContact waterfall enrichment and return the request handle. [write]

Safety

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

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

Resources