← 返回 Skills 市场
🔌

CompanyEnrich

作者 OOMOL · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ 安全检测通过
29
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install oo-companyenrich
功能描述
CompanyEnrich (companyenrich.com). Use this skill for ANY CompanyEnrich request — searching and reading data. Whenever a task involves CompanyEnrich, use thi...
使用说明 (SKILL.md)

CompanyEnrich

Operate CompanyEnrich through your OOMOL-connected account. This skill calls the companyenrich connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Category: Marketing, Data & Analytics. Exposes 6 action(s).

Running an action

Assume the user has already installed the oo CLI, signed in, and connected CompanyEnrich. 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 "companyenrich" --action "\x3Caction_name>"

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

oo connector run "companyenrich" --action "\x3Caction_name>" --data '\x3Cjson>' --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 below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with oo connector schema before constructing --data.

Available actions

Safety

  • Read actions (get / list / search) are safe to run directly.
  • Create, update, send, or post actions change CompanyEnrich state — confirm the exact payload and effect with the user before running.
  • Delete or remove actions are destructive — 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: \x3Chttps://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 — CompanyEnrich 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=companyenrich
    
  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

安全使用建议
Install this only if you intend to let your agent query CompanyEnrich through your OOMOL account. Review the `oo` CLI installer source and CompanyEnrich billing/credit implications before first setup, and keep user confirmation for any future connector action that would create, update, send, post, delete, or remove data.
能力标签
requires-sensitive-credentials
能力评估
Purpose & Capability
The stated purpose is to search, count, enrich, find similar companies, and inspect the current CompanyEnrich user through the `companyenrich` connector; the artifact files match that purpose.
Instruction Scope
Runtime instructions are scoped to `oo connector schema` and `oo connector run` for named CompanyEnrich actions, with guidance to inspect schemas before payload construction.
Install Mechanism
First-time setup includes remote installer commands for the `oo` CLI, but they are disclosed, conditional on `oo` being missing, and not the normal action path.
Credentials
The allowed tool pattern `Bash(oo *)` is broader than a single action command but proportionate for an OOMOL connector skill; no local file indexing, unrelated shell commands, or exfiltration instructions were found.
Persistence & Privilege
The skill requires an OOMOL-connected CompanyEnrich account/API key, with credentials handled server-side according to the artifact; no persistence, background workers, credential harvesting, or local token access is instructed.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install oo-companyenrich
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /oo-companyenrich 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.0
- Initial release of the `oo-companyenrich` skill for operating CompanyEnrich through an OOMOL-connected account via the `oo` CLI. - Supports company search workflows, including filtered company lookup, pagination, and matching company counts. - Adds enrichment actions for resolving company profiles by primary domain or identifying company properties. - Provides similar-company discovery from one or more seed company domains. - Includes account introspection through `get_current_user` to check the authenticated user summary and remaining capabilities. - Documents per-action schema inspection and execution commands, with guidance for authentication, connection, billing, and safety handling.
元数据
Slug oo-companyenrich
版本 1.0.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

CompanyEnrich 是什么?

CompanyEnrich (companyenrich.com). Use this skill for ANY CompanyEnrich request — searching and reading data. Whenever a task involves CompanyEnrich, use thi... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 29 次。

如何安装 CompanyEnrich?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install oo-companyenrich」即可一键安装,无需额外配置。

CompanyEnrich 是免费的吗?

是的,CompanyEnrich 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

CompanyEnrich 支持哪些平台?

CompanyEnrich 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 CompanyEnrich?

由 OOMOL(@oomol)开发并维护,当前版本 v1.0.0。

💬 留言讨论