# Agent QA Knowledge

Use when asked what an agent-qa run did, why a step passed or failed, what a run's...

- Repository: https://github.com/vostride/agent-qa (915 stars)
- Category: Testing
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add vostride/agent-qa --skill agent-qa-knowledge -g -a claude-code -y`
Codex: `npx skills add vostride/agent-qa --skill agent-qa-knowledge -g -a codex -y`
Cursor: `npx skills add vostride/agent-qa --skill agent-qa-knowledge -g -a cursor -y`
Gemini CLI: `npx skills add vostride/agent-qa --skill agent-qa-knowledge -g -a gemini-cli -y`

## Description

Use when asked what an agent-qa run did, why a step passed or failed, what a run's screenshots, console or network showed, what knowledge agent-qa learned or served, where a knowledge record came from, or which runs exist. Reads runs, evidence and knowledge through the agent-qa MCP tools or the agent-qa CLI with --json, never through .agent-qa files, SQLite or index files.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# agent-qa Knowledge

Get the whole picture first, then fetch only the piece the question needs.

## Workflow

1. Find the run with `agent_qa_list_runs`: completed runs, newest first, each naming its tests.
   Narrow it with `verdict`, `test`, `target`, `since` or `limit` when the question does.
2. Map it with `agent_qa_get_run_overview` and `{ "runId": "<runId>" }`. It lists every test and
   step with its verdict, screenshot shas, evidence kinds with counts, served records, whether a
   brief trace exists, and what the run learned. It carries addresses, not bodies.
3. Fetch only what the question needs, using the overview's addresses:
   - one step's document: `agent_qa_get_run_evidence` with `"action": "runs.evidence"`, `runId`,
     `testIndex`, `stepIndex` and `kind` (`console`, `network`, `a11y`, `aria` or `variables`;
     `subActionIndex` with `aria` only);
   - a screenshot: `agent_qa_get_run_evidence` with `"action": "runs.artifact"`, `runId` and
     `sha`. The answer is an image you can look at;
   - a record or a brief: the table below.
4. Answer with provenance: the run id, test and step numbers, and record ids you relied on.
   When a read says absent, withheld, not recorded or read error, say so and what it limits.

Test, step and sub-action numbers are zero-based, exactly as the overview prints them. Without
MCP, run the CLI verb from the project root. `--json` prints what the tool answers, except that
`npx agent-qa knowledge inspect` and `npx agent-qa knowledge diff <build>` print only the
`records` and `changes` array of that answer. `<build>` is a build ordinal or tag.
`npx agent-qa runs evidence <runId> --screenshot <sha> --out <file>` writes a screenshot to a new
file you then open with your image viewer.

## Questions → tools and verbs

The rest: https://github.com/vostride/agent-qa/blob/HEAD/packages/cli/skills/agent-qa-knowledge/SKILL.md