agentleFS
Sign inStart free
AtomicBot-aiAtomicBot-ai/atomicbot/.agents/skills/openclaw-qa-testing/SKILL.md

openclaw-qa-testing

Skill325 starsChanged 7 months agoMITView on GitHub

Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.

  • Reads credentials

We split this skill into the rules it gives an agent

10 rules. 4 are common, 1 is distinctive, and 5 are very specific to this project.

  • 4

    Common

    Most of the 12 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill for qa-lab / qa-channel work.

    line 8
  2. Distinctive:

    Only change model policy if the user explicitly asks.

    line 26
  3. Common:

    Read the seed plan and current suite implementation.

    line 30
  4. Very specific:

    If the user wants to watch the live UI, find the current openclaw-qa listen port and report http://127.0.0.1:<port>.

    line 49
  5. Common:

    If a scenario fails, fix the product or harness root cause, then rerun the full lane.

    line 50
  6. Common:

    prefer stable final reply evidence over transient child-session listing

    line 76
  7. Very specific:

    Add scenario metadata to qa/seed-scenarios.json

    line 82
  8. Very specific:

    Keep kickoff expectations in qa/QA_KICKOFF_TASK.md aligned

    line 83
  9. Very specific:

    Add executable coverage in extensions/qa-lab/src/suite.ts

    line 84
  10. Common:

    Prefer end-to-end assertions over mock-only checks

    line 85

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “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

OpenClaw QA Testing

Use this skill for qa-lab / qa-channel work. Repo-local QA only.

Read first

  • docs/concepts/qa-e2e-automation.md
  • docs/help/testing.md
  • docs/channels/qa-channel.md
  • qa/QA_KICKOFF_TASK.md
  • qa/seed-scenarios.json
  • extensions/qa-lab/src/suite.ts

Model policy

  • Live OpenAI lane: openai/gpt-5.4
  • Fast mode: on
  • Do not use:
    • openai/gpt-5.4-pro
    • openai/gpt-5.4-mini
  • Only change model policy if the user explicitly asks.

Default workflow

  1. Read the seed plan and current suite implementation.
  2. Decide lane:
    • mock/dev: mock-openai
    • real validation: live-openai
  3. For live OpenAI, use:
OPENCLAW_LIVE_OPENAI_KEY="${OPENAI_API_KEY}" \
pnpm openclaw qa suite \
  --provider-mode live-openai \
  --model openai/gpt-5.4 \
  --alt-model openai/gpt-5.4 \
  --fast \
  --output-dir .artifacts/qa-e2e/run-all-live-openai-<tag>
  1. Watch outputs:
    • summary: .artifacts/qa-e2e/run-all-live-openai-<tag>/qa-suite-summary.json
    • report: .artifacts/qa-e2e/run-all-live-openai-<tag>/qa-suite-report.md
  2. If the user wants to watch the live UI, find the current openclaw-qa listen port and report http://127.0.0.1:<port>.
  3. If a scenario fails, fix the product or harness root cause, then rerun the full lane.

Repo facts

  • Seed scenarios live in qa/.
  • Main live runner: extensions/qa-lab/src/suite.ts
  • QA lab server: extensions/qa-lab/src/lab-server.ts
  • Child gateway harness: extensions/qa-lab/src/gateway-child.ts
  • Synthetic channel: extensions/qa-channel/

What “done” looks like

  • Full suite green for the requested lane.
  • User gets:
    • watch URL if applicable
    • pass/fail counts
    • artifact paths
    • concise note on what was fixed

Common failure patterns

  • Live timeout too short:
    • widen live waits in extensions/qa-lab/src/suite.ts
  • Discovery cannot find repo files:
    • point prompts at repo/... inside seeded workspace
  • Subagent proof too brittle:
    • prefer stable final reply evidence over transient child-session listing
  • Harness “rebuild” delay:
    • dirty tree can trigger a pre-run build; expect that before ports appear

When adding scenarios

  • Add scenario metadata to qa/seed-scenarios.json
  • Keep kickoff expectations in qa/QA_KICKOFF_TASK.md aligned
  • Add executable coverage in extensions/qa-lab/src/suite.ts
  • Prefer end-to-end assertions over mock-only checks
  • Save outputs under .artifacts/qa-e2e/

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