Skip to main content

channel-message-flows

Use when running QA Lab channel message flow evidence.

来源信息

仓库
openclaw/openclaw
最近来源活动
2026年7月3日 04:48
检测到的 SKILL.md 语言
英语
星标
391,223
分支
82,236

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
channel-message-flows
description
Use when running QA Lab channel message flow evidence.
# Channel Message Flows Use this from the OpenClaw repo root to run the QA Lab evidence for Telegram draft/final delivery sequencing. The behavior is owned by one transport-native QA flow that can run through QA Channel or Crabline Telegram. ## QA Scenario Run the scenario through QA Lab: ```bash OPENCLAW_BUILD_PRIVATE_QA=1 node scripts/run-node.mjs qa suite \ --provider-mode mock-openai \ --scenario channel-message-flows \ --channel-driver qa-channel ``` Run the same YAML through the real Telegram plugin against Crabline's local provider server: ```bash OPENCLAW_BUILD_PRIVATE_QA=1 node scripts/run-node.mjs qa suite \ --provider-mode mock-openai \ --scenario channel-message-flows \ --channel-driver crabline \ --channel telegram ``` ## References - `qa/scenarios/channels/channel-message-flows.yaml` - `extensions/qa-channel/src/inbound.ts` - `extensions/qa-lab/src/qa-transport.ts` - `extensions/qa-lab/src/crabline-transport.ts` - `extensions/telegram/src/draft-stream.ts` The scenario covers `channels.streaming` as primary evidence and `runtime.delivery` as secondary evidence.
在 GitHub 查看