How do I install the QA Router skill?

Run npx skillmds@latest add majiayu000/qa-router 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 QA Router safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with QA Router?

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 QA Router free to use?

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

Who published QA Router?

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

QA Router by majiayu000 — Agent Skill

Name: QA Router
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

QA Skill Router

"Catalog of all QA tools - discover what you need, use what you choose."

Overview

This skill provides a complete catalog of available QA skills and sub-agents. It does not automatically load skills - the agent decides which tools to use based on task context.

Quick Reference: Validation Scenarios

Scenario	Skills	Sub-Agent
New Feature	`qa-test-creation` → `qa-code-review` → `qa-validation-workflow` → `qa-browser-testing`	`test-creator` → `qa-browser-validator`
Gameplay	`qa-test-creation` → `qa-gameplay-testing` → `qa-code-review`	`test-creator` → `qa-gameplay-tester`
Multiplayer	`qa-test-creation` → `qa-multiplayer-testing` → `qa-code-review`	`test-creator` → `qa-multiplayer-validator`
Visual/Shaders	`qa-test-creation` → `qa-visual-testing` → `qa-code-review`	`test-creator` → `visual-regression-tester`
Assets	`qa-validation-asset` → `qa-browser-testing`	`qa-browser-validator`
Bug Re-validation	`qa-code-review` → `qa-validation-workflow` → `qa-browser-testing`	`qa-browser-validator`

Quick Reference: By Validation Stage

Stage	Skills to Use
0. Session Start	`qa-workflow`, `qa-router` (this skill)
1. Message Queue	`shared-messaging`
2. Worktree Setup	`shared-worker`
3. Task Memory	`shared-retrospective`
4. Test Coverage	`qa-test-creation` (invokes `test-creator` if needed)
5. Test Execution	`qa-validation-workflow` (type-check → lint → test → build)
6. Code Review	`qa-code-review`
7. Browser Testing	`qa-browser-testing` + scenario-specific sub-agent
8. Bug Reporting	`qa-reporting-bug-reporting`

Decision Tree

START VALIDATION
        │
├─→ Task needs tests?
│   └─ Yes → Load qa-test-creation → test-creator sub-agent
│   └─ No → Continue
│
├─→ Run test execution (qa-validation-workflow)
│   └─ Tests fail?
│       ├─ Test code issue? → Fix test → Re-run
│       └─ Game code issue? → Bug report → Return to Developer
│
├─→ Code review needed?
│   ├─ Yes → Load qa-code-review
│   └─ No → Skip to browser testing
│
├─→ Task type?
│   ├─ Basic feature → qa-browser-testing + qa-browser-validator
│   ├─ Gameplay → qa-gameplay-testing + qa-gameplay-tester
│   ├─ Multiplayer → qa-multiplayer-testing + qa-multiplayer-validator
│   ├─ Visual/UI → qa-visual-testing + visual-regression-tester
│   └─ Assets → qa-validation-asset + qa-browser-validator
│
└─→ Validation failed?
    └─ Yes → qa-reporting-bug-reporting

Usage Pattern

1. Load skills: Use Skill("skill-name") or /skill-name
2. Validate: Execute validation workflow
3. Report: Use qa-reporting-bug-reporting if failed

---name: qa-routerdescription: Catalog of all QA skills and sub-agents. Exposes available tooling so the agent can decide what and when to use. Use when starting validation to discover appropriate testing tools.--- # QA Skill Router > "Catalog of all QA tools - discover what you need, use what you choose." ## Overview This skill provides a complete catalog of available QA skills and sub-agents. It does **not** automatically load skills - the agent decides which tools to use based on task context. ## Quick Reference: Validation Scenarios | Scenario | Skills | Sub-Agent | | --------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------- | | **New Feature** | `qa-test-creation` → `qa-code-review` → `qa-validation-workflow` → `qa-browser-testing` | `test-creator` → `qa-browser-validator` | | **Gameplay** | `qa-test-creation` → `qa-gameplay-testing` → `qa-code-review` | `test-creator` → `qa-gameplay-tester` | | **Multiplayer** | `qa-test-creation` → `qa-multiplayer-testing` → `qa-code-review` | `test-creator` → `qa-multiplayer-validator` | | **Visual/Shaders** | `qa-test-creation` → `qa-visual-testing` → `qa-code-review` | `test-creator` → `visual-regression-tester` | | **Assets** | `qa-validation-asset` → `qa-browser-testing` | `qa-browser-validator` | | **Bug Re-validation** | `qa-code-review` → `qa-validation-workflow` → `qa-browser-testing` | `qa-browser-validator` | ## Quick Reference: By Validation Stage | Stage | Skills to Use | | ---------------------- | ----------------------------------------------------------- | | **0. Session Start** | `qa-workflow`, `qa-router` (this skill) | | **1. Message Queue** | `shared-messaging` | | **2. Worktree Setup** | `shared-worker` | | **3. Task Memory** | `shared-retrospective` | | **4. Test Coverage** | `qa-test-creation` (invokes `test-creator` if needed) | | **5. Test Execution** | `qa-validation-workflow` (type-check → lint → test → build) | | **6. Code Review** | `qa-code-review` | | **7. Browser Testing** | `qa-browser-testing` + scenario-specific sub-agent | | **8. Bug Reporting** | `qa-reporting-bug-reporting` | ### Decision Tree ``` START VALIDATION │ ├─→ Task needs tests? │ └─ Yes → Load qa-test-creation → test-creator sub-agent │ └─ No → Continue │ ├─→ Run test execution (qa-validation-workflow) │ └─ Tests fail? │ ├─ Test code issue? → Fix test → Re-run │ └─ Game code issue? → Bug report → Return to Developer │ ├─→ Code review needed? │ ├─ Yes → Load qa-code-review │ └─ No → Skip to browser testing │ ├─→ Task type? │ ├─ Basic feature → qa-browser-testing + qa-browser-validator │ ├─ Gameplay → qa-gameplay-testing + qa-gameplay-tester │ ├─ Multiplayer → qa-multiplayer-testing + qa-multiplayer-validator │ ├─ Visual/UI → qa-visual-testing + visual-regression-tester │ └─ Assets → qa-validation-asset + qa-browser-validator │ └─→ Validation failed? └─ Yes → qa-reporting-bug-reporting ``` ## Usage Pattern ```markdown 1. Load skills: Use Skill("skill-name") or /skill-name 2. Validate: Execute validation workflow 3. Report: Use qa-reporting-bug-reporting if failed ```

Frequently asked questions

QA Router