Token导航 LogoToken导航

Agent Skill · 研究检索

yuboto-omni-api(yuboto omni API 搜索)

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

yuboto-omni-api 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 9,289。

总安装 14,544周安装 620GitHub Stars 1下载 4,752核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.6.2

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install yuboto-omni-api;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

yuboto-omni-api 怎么安装?

在终端执行 openclaw skills install yuboto-omni-api。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

yuboto-omni-api 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

yuboto-omni-api 需要什么权限?

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

yuboto-omni-api 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

yuboto-omni-api 用的人多吗?

公开数据是累计安装 14,544 次,近一周安装 620 次,下载 4,752 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

yuboto-omni-api 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
yuboto-omni-api

yuboto omni API 搜索 · 本页

14,5441接触敏感数据MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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.

平台分布

OpenClaw

94.59%
按下载量换算4,495

安全审计

VirusTotal

可疑

ClawScan

通过

Static analysis

未展示

权限和风险

接触敏感数据

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills