360 Secure SkillHub
360 安全技能中心

Encharge

该 Skill 借助 oo CLI 的 encharge 连接器操作 Encharge：先用 oo connector schema 获取动作的输入输出契约，再用 oo connector run 传入 JSON 参数执行动作。当前仅列出 send_email（写操作，发送事务邮件），凭证由 OOMOL 服务端注入，无需本地持有令牌。

oomol
oomol
热度 34.85
最近更新 2026-09-15 12:31:48
分类：营销依赖：代码执行 / 第三方 API / 读写文件应用场景：邮件起草

安装技能

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

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

Encharge

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

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

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

  • send_email — Send a transactional email through the current Encharge account. [write]

Safety

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

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

Resources