Channel Message Flows
Use when running QA Lab channel message flow evidence.
Get the complete skill folder, including its scripts and reference files.
This page is available to readers but is excluded from the public index, because it does not yet meet the evaluation standard.
When to use this skill
Use Channel Message Flows when an AI agent needs a reusable SKILL.md workflow for this job: Use when running QA Lab channel message flow evidence.
When not to use it
Skip Channel Message Flows when the task is outside the other category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/channel-message-flows # Save SKILL.md to ~/.claude/skills/channel-message-flows/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/channel-message-flows/SKILL.md. For a shared project, commit the folder at .claude/skills/channel-message-flows/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Channel Message Flows skill for this task: Use Channel Message Flows when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
66/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 64/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptinferred
The skill text mentions ChatGPT or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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.
Intended uses
- Use Channel Message Flows when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.