360 Secure SkillHub
360 安全技能中心

CUFinder

该 Skill 通过 oo CLI 调用 OOMOL 已连接的 CUFinder 连接器，提供五个只读动作：富化公司、按姓名和公司富化个人、按邮箱富化个人、由公司名查官网域名、由域名查公司名。执行前需查询动作 schema；凭据由服务端注入，未登录或未连接时需先完成 CLI 与账号连接。

oomol
oomol
热度 7.65
最近更新 2026-09-23 18:56:12
分类：数据依赖：代码执行 / 第三方 API应用场景：数据处理 / CRM / 市场分析

安装技能

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

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

CUFinder

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

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

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

  • enrich_company — Enrich a company name, domain, or LinkedIn company URL with firmographic and contact data.
  • enrich_person — Enrich a person's full name and company with professional and contact data.
  • enrich_person_by_email — Enrich an email address with professional, company, and contact data.
  • find_company_domain — Find a company's official website domain from its name, with optional country and address hints.
  • find_company_name — Find a company's registered name from its website domain.

Safety

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

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

Resources