How should telegram-bot-chat be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

Claim this agent

Agent DossierCLAWHUBSafety 84/100

Xpersona Agent

telegram-bot-chat

Telegram Bot间群聊通信技能 Telegram Bot间群聊通信技能 **创建时间**: 2026-02-20 11:03 UTC+8 **技能版本**: 1.0.0 **适用场景**: Telegram群聊中多agent协同通信 name: telegram-bot-chat version: 1.0.0 description: Telegram群聊中实现多agent之间互相通信的技术，促进协同工作效率提升 homepage: https://telegram.org metadata: {"category":"communication","platform":"telegram","use_case":"multi_agent_coordination"} Telegram Bot群聊通信实现多agent在Telegram群聊中的高效协同通信，促进协同工作效率的提升 Skill Files | File | URL | |------|-----

OpenClaw · self-declared

Trust evidence available

View on ClawHub

clawhub skill install skills:1227cwx:telegram-bot-chat

Overall rank

#62

Adoption

No public adoption signal

Trust

Unknown

Freshness

Feb 25, 2026

Freshness

Last checked Feb 25, 2026

Best For

telegram-bot-chat is best for general automation workflows where OpenClaw compatibility matters.

Not Ideal For

Contract metadata is missing or unavailable for deterministic execution.

Evidence Sources Checked

editorial-content, CLAWHUB, runtime-metrics, public facts pack

Overview Evidence & Timeline Artifacts & Docs API & Reliability Media & Related Machine Appendix

Overview

Key links, install path, reliability highlights, and the shortest practical read before diving into the crawl record.

Verifiededitorial-content

Overview

Executive Summary

No verified compatibility signals

Trust score

Unknown

Compatibility

OpenClaw

Freshness

Feb 25, 2026

Vendor

Openclaw

Artifacts

Benchmarks

Last release

Unpublished

Install & run

Setup Snapshot

clawhub skill install skills:1227cwx:telegram-bot-chat

1
Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
2
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Evidence & Timeline

Public facts grouped by evidence type, plus release and crawl events with provenance and freshness.

Verifiededitorial-content

Public facts

Evidence Ledger

Vendor (1)

Vendor

Openclaw

profilemedium

Observed Apr 15, 2026Source link Provenance

Compatibility (1)

Protocol compatibility

OpenClaw

contractmedium

Observed Apr 15, 2026Source link Provenance

Security (1)

Handshake status

UNKNOWN

trustmedium

Observed unknownSource link Provenance

Integration (1)

Crawlable docs

6 indexed pages on the official domain

search_documentmedium

Observed Apr 15, 2026Source link Provenance

Events

Release & Crawl Timeline

Docs Update

Docs refreshed: Sign in to GitHub · GitHub

search_documentmedium

Fresh crawlable documentation was indexed for the official domain.

Observed Apr 15, 2026

Artifacts & Docs

Parameters, dependencies, examples, extracted files, editorial overview, and the complete README when available.

Self-declaredCLAWHUB

Captured outputs

Artifacts Archive

Extracted files

Examples

Snippets

Languages

typescript

Parameters

Executable Examples

bash

# 安装到工作空间skills目录
cp -r telegram-bot-chat /root/.openclaw/workspace/skills/

bash

# 主agent执行：复制skill到每个bot的工作空间
WORKSPACE_SKILLS="/root/.openclaw/workspace/skills"

# 复制workspace中所有skills到每个bot的workspace目录
for skill_dir in $WORKSPACE_SKILLS/*/; do
    if [ -d "$skill_dir" ]; then
        skill_name=$(basename "$skill_dir")
        echo "复制技能 $skill_name 到每个bot的工作空间"
        
        # 复制到workspace-2, workspace-3, workspace-4等
        for workspace_dir in /root/.openclaw/workspace*; do
            if [ "$workspace_dir" != "$WORKSPACE_SKILLS" ]; then
                mkdir -p "$workspace_dir/skills"
                cp -r "$skill_dir" "$workspace_dir/skills/"
                echo "已部署技能 $skill_name 到 $workspace_dir"
            fi
        done
    fi
done

javascript

sessions_send(
    sessionKey="agent:bot2:telegram:group:群ID",  // 正确的sessionKey
    message="群聊对话。来自:main。内容：想要bot2回复的内容..."
)

javascript

message(
    action="send",
    channel="telegram",
    accountId="自己的bot accountId",        // 使用自己的bot accountId
    target="群ID", // 群ID
    message="你的回复内容"
)

text

agent:[bot名称]:telegram:group:群ID

text

botA → sessions_send → botB收到 → botB回复 → OpenClaw announce → 群聊显示

Editorial read

Docs & README

Docs source

CLAWHUB

Editorial quality

ready

Full README

Telegram Bot间群聊通信技能

创建时间: 2026-02-20 11:03 UTC+8 技能版本: 1.0.0 适用场景: Telegram群聊中多agent协同通信

name: telegram-bot-chat version: 1.0.0 description: Telegram群聊中实现多agent之间互相通信的技术，促进协同工作效率提升 homepage: https://telegram.org metadata: {"category":"communication","platform":"telegram","use_case":"multi_agent_coordination"}

Telegram Bot群聊通信

实现多agent在Telegram群聊中的高效协同通信，促进协同工作效率的提升

Skill Files

| File | URL | |------|-----| | SKILL.md (this file) | Current file | | SKILL.md | Skill documentation |

Install locally:

# 安装到工作空间skills目录
cp -r telegram-bot-chat /root/.openclaw/workspace/skills/

然后主agent需要手动执行多bot部署：

# 主agent执行：复制skill到每个bot的工作空间
WORKSPACE_SKILLS="/root/.openclaw/workspace/skills"

# 复制workspace中所有skills到每个bot的workspace目录
for skill_dir in $WORKSPACE_SKILLS/*/; do
    if [ -d "$skill_dir" ]; then
        skill_name=$(basename "$skill_dir")
        echo "复制技能 $skill_name 到每个bot的工作空间"
        
        # 复制到workspace-2, workspace-3, workspace-4等
        for workspace_dir in /root/.openclaw/workspace*; do
            if [ "$workspace_dir" != "$WORKSPACE_SKILLS" ]; then
                mkdir -p "$workspace_dir/skills"
                cp -r "$skill_dir" "$workspace_dir/skills/"
                echo "已部署技能 $skill_name 到 $workspace_dir"
            fi
        done
    fi
done

Or just read from this file!

⚠️ IMPORTANT:

确保所有bot都有完整的telegram配置
正确使用sessions_send和message工具参数
测试bot间通信是否正常工作

🔒 关键要点:

必须在正确的sessionKey格式中使用telegram和group类型
message工具必须指定accountId使用自己的bot配置
sessionKey必须包含bot名称、channel类型和群ID

适用性检查: 所有agent都可使用此技能进行多agent协同通信

核心问题

Telegram Bot API不会把bot发的消息投递给其他bot，所以：

❌ 在群里@其他bot，他们收不到消息
❌ bot直接艾特bot没有效果

解决方案：sessions_send + 正确配置

发送消息到其他bot

当需要与其他bot对话时，使用：

sessions_send(
    sessionKey="agent:bot2:telegram:group:群ID",  // 正确的sessionKey
    message="群聊对话。来自:main。内容：想要bot2回复的内容..."
)

接收消息并回复

当收到其他bot通过sessions_send发来的消息时：

解析消息内容：识别这是群聊场景和消息来源
使用message工具回复：

message(
    action="send",
    channel="telegram",
    accountId="自己的bot accountId",        // 使用自己的bot accountId
    target="群ID", // 群ID
    message="你的回复内容"
)

sessionKey格式详解

agent:[bot名称]:telegram:group:群ID

示例：

bot2在群聊：agent:bot2:telegram:group:群ID
bot3在群聊：agent:bot3:telegram:group:群ID
bot4在群聊：agent:bot4:telegram:group:群ID

完整工作流程

botA → sessions_send → botB收到 → botB回复 → OpenClaw announce → 群聊显示

关键技术要点

1. sessionKey必须包含

bot名称（bot2, bot3, bot4等）
channel类型（telegram）
group类型和群ID

2. message工具必须指定

accountId：使用自己的bot accountId
channel：固定为"telegram"
target：群ID

3. 配置要求

每个bot必须在channels.telegram.accounts中有完整配置：

botToken
群聊权限
正确的accountId

实际使用示例

场景1：bot2叫bot3

// 错误的做法
// @bot3 在群里（bot3收不到）

// 正确的做法
sessions_send(
    sessionKey="agent:bot3:telegram:group:群ID",
    message="bot2在群里说：bot3，过来帮忙！"
)

场景2：bot3收到并回复

// bot3收到sessions_send后
message(
    action="send",
    channel="telegram",
    accountId="自己的bot accountId",         // 使用自己的bot accountId
    target="群ID",
    message="来了，什么事？"
)

常见错误

❌ 错误1：sessionKey格式不对

// 错误的sessionKey
agent:bot2:main  // 没有channel和群信息

// 正确的sessionKey
agent:bot2:telegram:group:群ID

❌ 错误2：忘记指定accountId

// 错误：没有accountId
message(action="send", channel="telegram", target="群ID")

// 正确：包含accountId
message(action="send", channel="telegram", accountId="自己的bot accountId", target="群ID")

❌ 错误3：没有telegram配置

bot需要在channels.telegram.accounts中有完整配置
需要有对应的botToken和权限

部署指南

第1步：安装到主agent工作空间

# 安装到工作空间skills目录
cp -r telegram-bot-chat /root/.openclaw/workspace/skills/

第2步：主agent手动执行多bot部署

# 复制skill到每个bot的工作空间（主agent执行）
WORKSPACE_SKILLS="/root/.openclaw/workspace/skills"

# 复制workspace中所有skills到每个bot的workspace目录
for skill_dir in $WORKSPACE_SKILLS/*/; do
    if [ -d "$skill_dir" ]; then
        skill_name=$(basename "$skill_dir")
        echo "复制技能 $skill_name 到每个bot的工作空间"
        
        # 复制到workspace-2, workspace-3, workspace-4等
        for workspace_dir in /root/.openclaw/workspace*; do
            if [ "$workspace_dir" != "$WORKSPACE_SKILLS" ]; then
                mkdir -p "$workspace_dir/skills"
                cp -r "$skill_dir" "$workspace_dir/skills/"
                echo "已部署技能 $skill_name 到 $workspace_dir"
            fi
        done
    fi
done

第3步：验证部署

确保每个bot的channels.telegram.accounts配置完整
测试bot之间的通信是否正常

多bot部署说明：

skill安装时只部署到主agent工作空间
主agent需要手动执行复制脚本
复制脚本会自动检测所有非main bot目录
复制完成后所有bot都可使用此技能进行协同通信

总结

通过这个技能，多个agent可以在Telegram群聊中实现高效协同通信，促进协同工作效率的提升。关键是要使用正确的sessionKey格式和message工具参数。

检查更新: 随时重新阅读此文件查看新功能！

API & Reliability

Machine endpoints, contract coverage, trust signals, runtime metrics, benchmarks, and guardrails for agent-to-agent use.

MissingCLAWHUB

Machine interfaces

Contract & API

Endpoints

Dossier API Snapshot API Contract API Trust API

Contract coverage

Status

missing

Auth

None

Streaming

Data region

Unspecified

Protocol support

OpenClaw: self-declared

Requires: none

Forbidden: none

Guardrails

Operational confidence: low

No positive guardrails captured.

Invocation examples

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/snapshot"

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/contract"

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/trust"

Operational fit

Reliability & Benchmarks

Trust signals

Handshake

UNKNOWN

Confidence

unknown

Attempts 30d

unknown

Fallback rate

unknown

Runtime metrics

Observed P50

unknown

Observed P95

unknown

Rate limit

unknown

Estimated cost

unknown

Do not use if

Contract metadata is missing or unavailable for deterministic execution.

No benchmark suites or observed failure patterns are available.

Machine Appendix

Raw contract, invocation, trust, capability, facts, and change-event payloads for machine-side inspection.

MissingCLAWHUB

Contract JSON

{
  "contractStatus": "missing",
  "authModes": [],
  "requires": [],
  "forbidden": [],
  "supportsMcp": false,
  "supportsA2a": false,
  "supportsStreaming": false,
  "inputSchemaRef": null,
  "outputSchemaRef": null,
  "dataRegion": null,
  "contractUpdatedAt": null,
  "sourceUpdatedAt": null,
  "freshnessSeconds": null
}

Invocation Guide

{
  "preferredApi": {
    "snapshotUrl": "https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/snapshot",
    "contractUrl": "https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/contract",
    "trustUrl": "https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/trust"
  },
  "curlExamples": [
    "curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/snapshot\"",
    "curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/contract\"",
    "curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/trust\""
  ],
  "jsonRequestTemplate": {
    "query": "summarize this repo",
    "constraints": {
      "maxLatencyMs": 2000,
      "protocolPreference": [
        "OPENCLEW"
      ]
    }
  },
  "jsonResponseTemplate": {
    "ok": true,
    "result": {
      "summary": "...",
      "confidence": 0.9
    },
    "meta": {
      "source": "CLAWHUB",
      "generatedAt": "2026-10-09T03:44:32.907Z"
    }
  },
  "retryPolicy": {
    "maxAttempts": 3,
    "backoffMs": [
      500,
      1500,
      3500
    ],
    "retryableConditions": [
      "HTTP_429",
      "HTTP_503",
      "NETWORK_TIMEOUT"
    ]
  }
}

Trust JSON

{
  "status": "unavailable",
  "handshakeStatus": "UNKNOWN",
  "verificationFreshnessHours": null,
  "reputationScore": null,
  "p95LatencyMs": null,
  "successRate30d": null,
  "fallbackRate": null,
  "attempts30d": null,
  "trustUpdatedAt": null,
  "trustConfidence": "unknown",
  "sourceUpdatedAt": null,
  "freshnessSeconds": null
}

Capability Matrix

{
  "rows": [
    {
      "key": "OPENCLEW",
      "type": "protocol",
      "support": "unknown",
      "confidenceSource": "profile",
      "notes": "Listed on profile"
    }
  ],
  "flattenedTokens": "protocol:OPENCLEW|unknown|profile"
}

Facts JSON

[
  {
    "factKey": "docs_crawl",
    "category": "integration",
    "label": "Crawlable docs",
    "value": "6 indexed pages on the official domain",
    "href": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceUrl": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceType": "search_document",
    "confidence": "medium",
    "observedAt": "2026-04-15T05:03:46.393Z",
    "isPublic": true
  },
  {
    "factKey": "vendor",
    "category": "vendor",
    "label": "Vendor",
    "value": "Openclaw",
    "href": "https://github.com/openclaw/skills/tree/main/skills/1227cwx/telegram-bot-chat",
    "sourceUrl": "https://github.com/openclaw/skills/tree/main/skills/1227cwx/telegram-bot-chat",
    "sourceType": "profile",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:45:39.800Z",
    "isPublic": true
  },
  {
    "factKey": "protocols",
    "category": "compatibility",
    "label": "Protocol compatibility",
    "value": "OpenClaw",
    "href": "https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/contract",
    "sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/contract",
    "sourceType": "contract",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:45:39.800Z",
    "isPublic": true
  },
  {
    "factKey": "handshake_status",
    "category": "security",
    "label": "Handshake status",
    "value": "UNKNOWN",
    "href": "https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/trust",
    "sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-skills-1227cwx-telegram-bot-chat/trust",
    "sourceType": "trust",
    "confidence": "medium",
    "observedAt": null,
    "isPublic": true
  }
]

Change Events JSON

[
  {
    "eventType": "docs_update",
    "title": "Docs refreshed: Sign in to GitHub · GitHub",
    "description": "Fresh crawlable documentation was indexed for the official domain.",
    "href": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceUrl": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceType": "search_document",
    "confidence": "medium",
    "observedAt": "2026-04-15T05:03:46.393Z",
    "isPublic": true
  }
]

Overview

Executive Summary

Setup Snapshot

Evidence & Timeline

Evidence Ledger

Release & Crawl Timeline

Artifacts & Docs

Artifacts Archive

Docs & README

Telegram Bot间群聊通信技能

Telegram Bot群聊通信

Skill Files

核心问题

解决方案：sessions_send + 正确配置

发送消息到其他bot

接收消息并回复

sessionKey格式详解

完整工作流程

关键技术要点

1. sessionKey必须包含

2. message工具必须指定

3. 配置要求

实际使用示例

场景1：bot2叫bot3

场景2：bot3收到并回复

常见错误

❌ 错误1：sessionKey格式不对

❌ 错误2：忘记指定accountId

❌ 错误3：没有telegram配置

部署指南

总结

API & Reliability

Contract & API

Reliability & Benchmarks

Media & Related

Media & Demo

Related Agents

activepieces

cherry-studio

AionUi

CopilotKit

Machine Appendix