Token导航 LogoToken导航TokenDH.com
研究检索敏感数据clawhub未标认证来源可访问clear审计提醒

yuboto-omni-apiyuboto omni API 搜索

Agent Skill

用于辅助 API 设计、接口文档、请求响应结构和服务集成说明。它适合让 Agent 梳理 endpoint、生成 OpenAPI 草稿、检查字段命名、整理错误码或辅助前后端联调。使用时需要确认真实业务语义、鉴权方式、分页和错误处理规则;涉及生成接口文档时,应避免凭空补字段,最好从现有代码、schema 或接口样例中提取事实。

总安装

14,544

周安装

620

GitHub Stars

1

下载量

4,752
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:yuboto-omni-api(yuboto omni API 搜索)
来源仓库:https://github.com/dinaras/yuboto-omni-api
安装命令:
openclaw skills install yuboto-omni-api
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install yuboto-omni-api

简介

为 Yuboto Omni API(SMS/Viber/消息端点、回调、列表/联系人/黑名单、成本/余额/账户)实施、故障排除和生成集成

SKILL.md

name
yuboto-omni-api
description
Implement, troubleshoot, and generate integrations for Yuboto Omni API (SMS/Viber/messaging endpoints, callbacks, lists/contacts/blacklist, cost/balance/account methods). Use when building code or workflows against Yuboto API docs, especially when endpoint details differ between PDF docs and live Swagger.
metadata

Yuboto Omni API

Use this skill to work with Yuboto Omni API safely and consistently.

Note: This skill requires the OCTAPUSH_API_KEY environment variable.

Getting Started: You need a Yuboto/Octapush account with API access. Register at octapush.yuboto.com and request API access from support.

OpenClaw Integration: This skill supports native OpenClaw credential management. Store your API key in openclaw.json for centralized, secure credential handling.

Source-of-truth order

  1. references/swagger_v1.json (live endpoint contract)
  2. references/api_quick_reference.md (human-readable endpoint map)
  3. references/omni_api_v1_10_raw.md (legacy PDF extract)
  4. assets/OMNI_API_DOCUMENTATION_V1_10.pdf (original PDF)

If PDF and Swagger conflict, prefer Swagger for endpoint paths/fields.

Fast workflow

  1. Identify the use case (send message, get DLR, contacts, subscriber lists, blacklist, cost/balance).
  2. Find matching endpoint(s):

- Read references/api_quick_reference.md, or - Run: python3 scripts/find_endpoints.py --q "<keyword>"

  1. Validate request schema directly in references/swagger_v1.json:

- parameters (path/query/header) - requestBody - response schema

  1. Build implementation code with:

- clear auth header handling - retries + timeout - structured error mapping

  1. For advanced Viber features, check Swagger first.

Available commands (provided by scripts/yuboto_cli.py)

  • balance — get account balance
  • cost --channel sms --iso2 gr --phonenumber +30... — estimate sending cost
  • send-sms --sender <approved_sender> --text "..." --to +30... --batch-size 200 --sms-encoding auto — send SMS (auto-batched + auto Unicode/GSM)
  • dlr --id <messageGuid> — check delivery status for one message
  • send-csv --file contacts.csv --phone-col phonenumber --text-col text --sender-col sender — bulk send from CSV
  • poll-pending — refresh statuses for all pending messages
  • history --last 20 — show recent send records
  • status / status --id <messageGuid> — inspect tracked message state

Output requirements

When generating code or integration instructions:

  • Include exact method + path.
  • Include required auth headers.
  • Include minimal working request example.
  • Include expected response shape.
  • Include 1 failure case and handling.

Environment Variables

Required Credential

  • OCTAPUSH_API_KEY — Your Yuboto/Octapush API key (already base64 encoded from Octapush)

Note: This is the only credential required.

Optional Variables (for testing/overrides)

  • TEST_PHONENUMBER — Phone number for testing (international format: +3069XXXXXXXX)
  • SMS_SENDER — Default sender ID for SMS messages (must be approved)
  • YUBOTO_BASE_URL — Override API base URL (default: https://api.yuboto.com)

Getting an API Key

To use this skill, you need a Yuboto/Octapush API key:

  1. Register for an account at octapush.yuboto.com
  2. Contact Yuboto support to request API access
  3. Get your API key from your Octapush dashboard or via support

The API key is used for authentication with all Yuboto Omni API endpoints.

Setup Instructions

Option 1: OpenClaw Config (✅ Recommended)

Add to your openclaw.json config file:

"skills": {
  "entries": {
    "yuboto-omni-api": {
      "enabled": true,
      "env": {
        "OCTAPUSH_API_KEY": "your_base64_api_key_here"
      }
    }
  }
}

Option 2: Environment Variable

export OCTAPUSH_API_KEY="your_base64_api_key_here"

Note: .env files are not supported. Use OpenClaw config for secure, centralized credential management.

Security + Ops Notes

  • Store API key in environment variable OCTAPUSH_API_KEY, not in source files.
  • Prefer env vars over CLI --api-key to avoid leaking credentials in shell history.
  • poll_pending.sh reads OCTAPUSH_API_KEY from the process environment only (it does not source .env).
  • Always use an account-approved sender ID for SMS. If sender is not approved, API returns 108 - Sms Sender is not valid.
  • Bulk safety defaults are enabled:

- send-sms defaults to --batch-size 200 (hard cap 1000 recipients/request) - send-sms defaults to --batch-delay-ms 250 - send-csv defaults to --delay-ms 100

  • Encoding defaults:

- --sms-encoding auto detects non-GSM text and sends as Unicode - Force Unicode with --sms-encoding unicode for scripts like Greek/Arabic/Chinese - Force GSM-7 with --sms-encoding gsm when needed

  • Local state retention is enabled by default:

- Sent log rotates to last 5000 lines (YUBOTO_MAX_SENT_LOG_LINES) - State index keeps up to 5000 tracked IDs (YUBOTO_MAX_STATE_RECORDS)

  • Runtime data location default is outside the skill folder:

- CLI state default: $XDG_STATE_HOME/openclaw/yuboto-omni-api (fallback ~/.local/state/openclaw/yuboto-omni-api) - Poll logs/state default under the same base (YUBOTO_LOG_DIR/YUBOTO_STATE_DIR override supported)

  • Privacy-by-default storage:

- Stored state/log keeps minimal metadata (messageGuid, timestamps, status, recipient count) - Full payload/text/recipient persistence is off by default - Enable full persistence only if needed via YUBOTO_STORE_FULL_PAYLOAD=true

  • Runtime dependency model: Python standard library only (no requests install required).
  • Helper scripts are also stdlib-only: scripts/refresh_swagger.py uses urllib (no pip installs).
  • Treat local runtime logs/state as sensitive even in minimized mode.

Notes

  • Swagger URL: https://api.yuboto.com/scalar/#description/introduction
  • Swagger JSON: https://api.yuboto.com/swagger/v1/swagger.json
  • More product/account info: https://messaging.yuboto.com
  • Keep generated examples language-neutral unless user requests GR/EN copy.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

94.59%
按下载量换算4,495

安全审计

VirusTotal

可疑

ClawScan

通过

Static analysis

未展示

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills