菜单
Use when running QA Lab channel message flow evidence.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.
Summarize CodexBar local cost logs by model for Codex or Claude, including current or full breakdowns.
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.
Triage, redact, clean up, and resolve OpenClaw GitHub Secret Scanning alerts in issues or PRs.
Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.
Search ClawHub for skills when a requested capability is not already available; install, verify, update, publish, or sync skills.
| 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.