360 Secure SkillHub
360 安全技能中心

Moxie

该 Skill 通过 OOMOL 的 oo CLI 调用 moxie 连接器，提供六个只读 action：列出客户、销售流程阶段、任务阶段，以及按名称、联系信息、邮箱或客户搜索客户、联系人与项目。使用前先查询 action schema，再以 JSON 参数运行；凭据由 OOMOL 服务端注入，CLI 安装与登录仅在命令报错时按提示处理。

oomol
oomol
热度 24.25
最近更新 2026-09-15 13:25:28
分类：搜索依赖：代码执行 / 第三方 API应用场景：CRM / 任务管理

安装技能

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

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

Moxie

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

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

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

  • list_clients — List all clients in the connected Moxie workspace.
  • list_pipeline_stages — List sales pipeline stages configured in the Moxie workspace.
  • list_task_stages — List project task stages configured in the Moxie workspace.
  • search_clients — Search Moxie clients by client name or contact information.
  • search_contacts — Search Moxie contacts by first name, last name, or email address.
  • search_projects — Search active Moxie projects, optionally filtering by client name.

Safety

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

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

Resources