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: Run the same YAML through the real Telegram plugin against Crabline's local provider server: References The scenario covers as primary evidence and as secondary evidence.
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/channel-message-flows · pinned to the source commit
git clone https://github.com/openclaw/openclaw.git
cd openclaw
git checkout b1e27db51ce36bc26669f6a00d7990908a481ff6
mkdir -p ".claude/skills/channel-message-flows"
cp -r ".agents/skills/channel-message-flows" ".claude/skills/channel-message-flows"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit b1e27db51ce3. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.