agentleFS
Sign inStart free
bighamxbighamx/openclaw-android-node-apk/.agents/skills/channel-message-flows/SKILL.md

channel-message-flows

Skill59 starsChanged 16 days agoMITView on GitHub

Use when running QA Lab channel message flow evidence.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this from the OpenClaw repo root to run the QA Lab evidence for Telegram draft/final delivery sequencing.

    line 8
  2. Distinctive:

    Run the scenario through QA Lab:

    line 14
  3. Distinctive:

    Run the same YAML through the real Telegram plugin against Crabline's local provider server:

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

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

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free