Testing Skill Discovery (English)

Chinese version: See the corresponding Chinese skill.

When to Use

• Need to decide which testing skill should be used before execution.
• The request mixes multiple testing directions or phases.

Full inventory and availability

Read references/skill-capability-inventory.json to check exact canonical IDs. This 2026-10-12 snapshot catalogs 165 IDs; catalog existence does not prove installation or callability on the current Host. Missing installation evidence means availability=UNKNOWN; explicitly absent means UNAVAILABLE. Match explicit specialties (authentication vs authorization, retrieval vs answer quality, impact scope vs regression selection) before broad Composition routes. Keep one primary and at most one helper. For an unavailable target, state the gap and minimal installation/handoff action without claiming invocation.

Workflow

1. Read the same-directory reference.md first and match one structured route when applicable; it is the only Composition reference required for independent installation.
2. Read the user request and first identify the capability stage (Core QA / Engineering QA / Production Quality / AI Native QA) and primary testing goal.
3. Follow the routing prompt under prompts/: pick 1 primary skill; add at most 1 helper only when needed.
4. Hand the request to the target skill; do not execute the full testing work inside this router skill.