About channel-message-flows
Channel Message Flows is an OpenClaw QA skill for testing the sequence of Telegram draft and final message delivery. It runs one scenario through QA Channel or the Telegram plugin with Crabline.
Key features
- 01Run the flow through QA Lab
- 02Test with QA Channel
- 03Test via Telegram and Crabline
- 04Collect streaming and delivery evidence
Use cases
- 01Check Telegram draft-to-final delivery order
- 02Run the scenario with a mock provider
- 03Compare QA Channel and Telegram transport behavior
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ openclaw/ openclaw --skill channel-message-flowsAfter installing, type/channel-message-flowsin Claude Code to confirm it loaded.
Details
From the project READMEChannel 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:
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:
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.yamlextensions/qa-channel/src/inbound.tsextensions/qa-lab/src/qa-transport.tsextensions/qa-lab/src/crabline-transport.tsextensions/telegram/src/draft-stream.ts
The scenario covers channels.streaming as primary evidence and
runtime.delivery as secondary evidence.