with one click
channel-message-flows
Use when running QA Lab channel message flow evidence.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Use when running QA Lab channel message flow evidence.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use the diffs tool to produce real, shareable diffs (viewer URL, file artifact, or both) instead of manual edit summaries.
Use the imsg CLI from OpenClaw agents for iMessage/SMS DMs, groups, replies, reactions, polls, watching, and private-API actions.
Pre-commit/ship code review: Codex default; optional Claude, Pi, Droid, Copilot, Cursor, or OpenCode.
Use immediately for any pasted OpenClaw GitHub issue or PR URL/number, and for OpenClaw issue/PR review, triage, duplicate search, opener identity/who wrote it, author account age/activity, comments, labels, close, land, or maintainer evidence checks.
Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.
Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
| name | channel-message-flows |
| description | Use when running QA Lab channel message flow evidence. |
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.
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
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.tsThe scenario covers channels.streaming as primary evidence and
runtime.delivery as secondary evidence.