Use when creating, editing, validating, or running agent-qa tests, suites, or hooks. Prefer agent-qa MCP tools, enforce canonical agent-qa IDs, and use the bundled schema reference to avoid hallucinated config keys or YAML fields.
SkillScore78Maintained
Automatic
◆QA & Test Engineering pack
Last verified 9/8/2026
What it changes
Passed 16 of 20 test cases with the skill, and 3 of 20 without it.
Without skill13%
With skill78%
Checks it passed that the model alone missed
States that run IDs start with the prefix r_.
States that test IDs start with the prefix t_.
States that hook IDs start with the prefix h_.
and 14 more in the full report
17 fixed1 passed either way3 still failing2 broke
Pass-rate lift
+65 pp
Tokens
-34%
Agent turns
0%
Response time
-45%
Model gemini-3.6-flashMeasured 9/8/2026v118 of 23 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 17
Prompt
When validating a suite object using `agent_qa_validate_definition` before saving, what exact string value must be assigned to the `kind` field?
What was checked, without and with the skill
Checked
Without skill
With skill
Sets the kind parameter to suite when validating suite definitions with agent_qa_validate_definition.
Missed
Passed
case-10 · gemini-3.6-flash · 9/8/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md42 lines2 files
agent-qa Authoring
Workflow
Discover the local surface with agent_qa_discover.
Inspect active config with agent_qa_get_config, especially targets, devices, providers, and services.mcp.
Load references/agent-qa-contracts.json when you need exact schema fields or ID contracts.
Search the user's past AI coding sessions with the deja CLI. Use when they say things like 'didn't we fix this before', 'what did we decide about X', or before re-debugging an error that may already be solved.