Menú
Use when running QA Lab channel message flow evidence.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
QQBot rich media send and receive support. Use <qqmedia> tags only for explicit media send/view requests, treating inbound attachment paths as private current-conversation context.
Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push debounce, shard sizing, hosted-runner offload, queue health, and safe ramp-down/ramp-up changes. Use when tuning `.github/workflows/*`, `docs/ci.md`, CI runner labels, matrix `max-parallel`, ClawSweeper/Blacksmith burst protection, CodeQL runner placement, or investigating slow/queued OpenClaw CI.
Prepare or verify OpenClaw stable/beta releases, changelogs, release notes, publish commands, and artifacts.
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.
Regenerate OpenClaw release changelog sections from git history before beta or stable releases.
| 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. This skill no longer launches a standalone script; the behavior is owned by the QA scenario and its Vitest-backed e2e test.
Run the scenario through QA Lab:
pnpm openclaw qa suite --scenario channel-message-flows
Run the focused e2e test directly in a Codex worktree:
node scripts/run-vitest.mjs extensions/telegram/src/channel-message-flows.qa.e2e.test.ts
qa/scenarios/channels/channel-message-flows.yamlextensions/telegram/src/channel-message-flows.qa.e2e.test.tsextensions/telegram/src/test-support/channel-message-flows.tsThe scenario covers channels.streaming as primary evidence and records
secondary coverage for thread preservation, delivery ordering, and reasoning
preview visibility.