360 Secure SkillHub
360 安全技能中心

MOCO

该 Skill 通过 oo CLI 调用 OOMOL 托管连接器访问 MOCO，提供查询公司、联系人和当前用户资料等只读动作；执行前可用 schema 命令查看权威输入输出字段，凭据由服务端注入，无需本地管理令牌。

oomol
oomol
热度 42.65
最近更新 2026-09-15 12:48:50
分类：搜索依赖：代码执行 / 第三方 API应用场景：CRM / API 集成 / 研究

安装技能

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

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

MOCO

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

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

oo connector run "moco" --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_company — Retrieve one MOCO company by ID.
  • get_contact — Retrieve one MOCO contact person by ID.
  • get_profile — Retrieve the current MOCO user's profile.
  • list_companies — List MOCO companies with official filters and response-header pagination.
  • list_contacts — List MOCO contact people with official filters and response-header pagination.

Safety

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

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

Resources