How do I install the Openclaw QA Testing skill?

Run npx skillmds@latest add iamlukethedev/openclaw-qa-testing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openclaw QA Testing safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openclaw QA Testing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openclaw QA Testing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openclaw QA Testing?

iamlukethedev (@iamlukethedev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openclaw QA Testing by iamlukethedev

Name: Openclaw QA Testing
Author: iamlukethedev

Openclaw QA Testing

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.

iamlukethedev 2739ee5 2 files · 3.1 KB Updated Sep 17, 2026

File contents

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

Read the seed plan and current suite implementation.
Decide lane:
- mock/dev: mock-openai
- real validation: live-openai
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 \
  --output-dir .artifacts/qa-e2e/run-all-live-openai-<tag>

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

---name: openclaw-qa-testingdescription: 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.---# OpenClaw QA TestingUse 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 workflow1. Read the seed plan and current suite implementation.2. Decide lane: - mock/dev: `mock-openai` - real validation: `live-openai`3. For live OpenAI, use:```bashOPENCLAW_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 \ --output-dir .artifacts/qa-e2e/run-all-live-openai-<tag>```4. 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`5. If the user wants to watch the live UI, find the current `openclaw-qa` listen port and report `http://127.0.0.1:<port>`.6. 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/`

Frequently asked questions