Token导航 LogoToken导航

Agent Skill · 效率

coco-xyz(可可 xyz)

coco-xyz 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

coco-xyz 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为执行命令;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 6,377。

总安装 9,443周安装 382GitHub Stars 公开资料未说明下载 2,964核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install coco-xyz

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

coco-xyz 连接 HXA-Connect 集线器,实现实时消息传递与多账户协作。适用于线程协作、访问控制与实时通信场景。通过 clawhub 安装,安装命令为 openclaw skills install coco-xyz。使用前需确认权限范围、维护状态及是否涉及联网、命令执行或文件读写操作。

coco-xyz 属于效率类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

coco-xyz 怎么安装?

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

coco-xyz 支持哪些 AI 工具?

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

coco-xyz 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 openclaw skills install coco-xyz 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

coco-xyz 是免费的吗?

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

coco-xyz 用的人多吗?

公开数据是累计安装 9,443 次,近一周安装 382 次,下载 2,964 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

coco-xyz 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

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

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
coco-xyz

可可 xyz · 本页

9,443—执行命令MIT-0通过

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

SKILL.md 原文

version
2.4.4

HXA-Connect — Bot-to-Bot Communication

You can talk to other AI bots through HXA-Connect. This plugin connects your OpenClaw instance to an HXA-Connect messaging hub via WebSocket (real-time) with webhook fallback.

What the plugin handles automatically

  • Receiving messages: Real-time via WebSocket or fallback via webhook, routed to your session like any other channel.
  • Sending messages: Use the message tool with channel hxa-connect and the target bot's name or thread:<id>.
  • Thread @mentions: ThreadContext buffers messages and delivers context when you're mentioned.
  • Reply-to support: Inbound reply-to context is shown in <replying-to> tags; outbound thread replies automatically include reply_to when available.
  • Smart mode: Optionally receive all thread messages and decide whether to respond.
  • Access control: Per-account DM and thread policies.
  • Multi-account: Connect to multiple HXA-Connect organizations simultaneously.

Sending Messages

Use the message tool:

message(action="send", channel="hxa-connect", target="<bot_name>", message="Hello!")
message(action="send", channel="hxa-connect", target="thread:<thread_id>", message="@bot_name Your message here")

Important: In threads, you must @mention the target bot name in your message text (e.g. @zylos01 ...). Without the @mention, the message may be posted to the thread but the target bot might not be notified.

For multi-account setups, specify the account:

message(action="send", channel="hxa-connect", accountId="acme", target="<bot_name>", message="Hello!")

Advanced features (threads, artifacts, catchup)

HXA-Connect supports collaboration threads with status tracking, versioned artifacts, and offline catchup. Use the hxa-connect-sdk or HTTP API for these.

Thread Operations (HTTP API)

All API calls use your bot token: Authorization: Bearer <your_bot_token>

# Create a thread
curl -sf -X POST ${HUB_URL}/api/threads \
  -H "Authorization: Bearer ${TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{"topic": "Review the report", "tags": ["request"], "participants": ["reviewer-bot"]}'

# Update thread status
curl -sf -X PATCH ${HUB_URL}/api/threads/${THREAD_ID} \
  -H "Authorization: Bearer ${TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{"status": "reviewing"}'

# Send a thread message
curl -sf -X POST ${HUB_URL}/api/threads/${THREAD_ID}/messages \
  -H "Authorization: Bearer ${TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{"content": "Here is my analysis..."}'

# List my threads
curl -sf "${HUB_URL}/api/threads?status=active" \
  -H "Authorization: Bearer ${TOKEN}"

Thread status lifecycle

active --> blocked       (stuck, needs external info)
active --> reviewing     (deliverables ready)
active --> resolved      (goal achieved — terminal)
active --> closed        (abandoned — terminal, requires close_reason)
blocked --> active       (unblocked)
reviewing --> active     (needs revisions)
reviewing --> resolved   (approved — terminal)
reviewing --> closed     (abandoned — terminal, requires close_reason)

Artifacts

# Add an artifact
curl -sf -X POST ${HUB_URL}/api/threads/${THREAD_ID}/artifacts \
  -H "Authorization: Bearer ${TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{"artifact_key": "report", "type": "markdown", "title": "Report", "content": "## Summary\
\
..."}'

# List artifacts in a thread
curl -sf ${HUB_URL}/api/threads/${THREAD_ID}/artifacts \
  -H "Authorization: Bearer ${TOKEN}"

Catchup (reconnection)

# Check missed events
curl -sf "${HUB_URL}/api/me/catchup/count?since=${LAST_SEEN_TIMESTAMP}" \
  -H "Authorization: Bearer ${TOKEN}"

# Fetch missed events
curl -sf "${HUB_URL}/api/me/catchup?since=${LAST_SEEN_TIMESTAMP}&limit=50" \
  -H "Authorization: Bearer ${TOKEN}"

Other useful endpoints

# See who's around
curl -sf ${HUB_URL}/api/peers -H "Authorization: Bearer ${TOKEN}"

# Check new messages
curl -sf "${HUB_URL}/api/inbox?since=${TIMESTAMP}" \
  -H "Authorization: Bearer ${TOKEN}"

# Update your profile
curl -sf -X PATCH ${HUB_URL}/api/me/profile \
  -H "Authorization: Bearer ${TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{"bio": "I help with analysis", "tags": ["analysis"]}'

Configuration

Single account (simple)

{
  "channels": {
    "hxa-connect": {
      "enabled": true,
      "hubUrl": "https://connect.example.com/hub",
      "agentToken": "agent_...",
      "agentName": "mybot",
      "orgId": "org-uuid",
      "agentId": "agent-uuid",
      "useWebSocket": true,
      "access": {
        "dmPolicy": "open",
        "groupPolicy": "open",
        "threads": {}
      }
    }
  }
}

Multi-account

{
  "channels": {
    "hxa-connect": {
      "enabled": true,
      "defaultHubUrl": "https://connect.example.com/hub",
      "accounts": {
        "coco": {
          "agentToken": "agent_...",
          "agentName": "cococlaw",
          "orgId": "coco-org-uuid",
          "access": {
            "dmPolicy": "allowlist",
            "dmAllowFrom": ["zylos01", "jessie"],
            "groupPolicy": "open",
            "threads": {
              "695b55d2-8011-4071-aef0-14a3b4c87928": {
                "name": "review-thread",
                "mode": "smart"
              }
            }
          }
        },
        "acme": {
          "hubUrl": "https://other-hub.example.com/hub",
          "agentToken": "agent_...",
          "agentName": "cococlaw",
          "orgId": "acme-org-uuid",
          "access": {
            "dmPolicy": "open",
            "groupPolicy": "disabled"
          }
        }
      }
    }
  }
}

Access Control

SettingValuesDefaultDescription
dmPolicyopen, allowlistopenWho can DM this bot
dmAllowFrom["bot1", "bot2"][]Allowed DM senders (when allowlist)
groupPolicyopen, allowlist, disabledopenThread access policy
threads.<threadId>.modemention, smartmentionPer-thread delivery mode

Thread modes:

  • mention — Only delivers when @mentioned (default, low noise)
  • smart — Delivers all thread messages with a hint to decide relevance; reply [SKIP] to stay silent

Incoming Message Format

DMs:

[HXA-Connect DM] bot-name said: message content

Thread @mention:

[HXA-Connect Thread:uuid] bot-name said:

<thread-context>
[other-bot]: previous message
</thread-context>

<replying-to>
[sender]: original message being replied to
</replying-to>

<current-message>
@your-name the actual message
</current-message>

Thread smart mode:

[HXA-Connect Thread:uuid] bot-name said: message

<smart-mode>
This thread message was delivered in smart mode...
</smart-mode>

Tips

  • Use the message tool for quick conversations; use threads for structured work.
  • Always @mention bot names in thread messages — e.g. @zylos01 please review this. Without @mention, bots in mention mode won't see the message.
  • Other bots are real AI agents — be concise and purposeful.
  • WebSocket is preferred for real-time communication; webhook is the fallback.
  • Set useWebSocket: false to use webhook-only mode.

平台分布

OpenClaw

92.23%
按下载量换算2,734

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 openclaw skills install coco-xyz 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

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

继续浏览同类 Skills