/agent-qa-result-triage
Use when investigating failed agent-qa runs, inspecting artifacts, classifying failures, or comparing recent runs. Prefer agent-qa MCP run/artifact tools and produce evidence-backed triage.
$ npx -y skills add vostride/agent-qa --skill agent-qa-result-triage --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/agent-qa-result-triage
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when investigating failed agent-qa runs, inspecting artifacts, classifying failures, or comparing recent runs. Prefer agent-qa MCP run/artifact tools and produce evidence-backed triage.
SKILL.md
agent-qa-result-triage.SKILL.mdname: agent-qa-result-triage
description: Use when investigating failed agent-qa runs, inspecting artifacts, classifying failures, or comparing recent runs. Prefer agent-qa MCP run/artifact tools and produce evidence-backed triage.
metadata:
short-description: Triage agent-qa run failures
agent-qa Result Triage
Workflow
1. Start with `agent_qa_get_run` for run status, suite child context, steps, and attempts. 2. Fetch evidence before deciding:
- `agent_qa_get_run_artifact`
- `agent_qa_get_run_steps`
- `agent_qa_get_run_logs`
- `agent_qa_get_run_execution_logs`
3. Call `agent_qa_classify_failure` and use its category as the default classification unless stronger evidence contradicts it. 4. Compare recent related runs when available in the classifier output. 5. Return a concise triage result: category, confidence, evidence, likely fix area, and next action. 6. For code changes, switch to `agent-qa-debug-fix` after triage is complete.
Categories
Use one of the fixed categories from `references/triage-categories.md`:
- `timeout`
- `appium_startup`
- `browser_disconnect`
- `element_not_found`
- `assertion_failure`
- `hook_failure`
- `infrastructure`
- `unknown_failure`
Evidence Rules
- Quote or summarize concrete artifact/log/step evidence.
- Mention missing artifact sections if they limit confidence.
- Do not invent screenshots, videos, logs, or memory context that was not returned by MCP.
- If MCP is unavailable, use dashboard REST APIs or `agent-qa` CLI output as fallback and say which evidence was unavailable.
Read more
name: agent-qa-result-triage description: Use when investigating failed agent-qa runs, inspecting artifacts, classifying failures, or comparing recent runs. Prefer agent-qa MCP run/artifact tools and produce evidence-backed triage. metadata: short-description: Triage agent-qa run failures
agent-qa Result Triage
Workflow
1. Start with `agent_qa_get_run` for run status, suite child context, steps, and attempts. 2. Fetch evidence before deciding:
- `agent_qa_get_run_artifact`
- `agent_qa_get_run_steps`
- `agent_qa_get_run_logs`
- `agent_qa_get_run_execution_logs`
3. Call `agent_qa_classify_failure` and use its category as the default classification unless stronger evidence contradicts it. 4. Compare recent related runs when available in the classifier output. 5. Return a concise triage result: category, confidence, evidence, likely fix area, and next action. 6. For code changes, switch to `agent-qa-debug-fix` after triage is complete.
Categories
Use one of the fixed categories from `references/triage-categories.md`:
- `timeout`
- `appium_startup`
- `browser_disconnect`
- `element_not_found`
- `assertion_failure`
- `hook_failure`
- `infrastructure`
- `unknown_failure`
Evidence Rules
- Quote or summarize concrete artifact/log/step evidence.
- Mention missing artifact sections if they limit confidence.
- Do not invent screenshots, videos, logs, or memory context that was not returned by MCP.
- If MCP is unavailable, use dashboard REST APIs or `agent-qa` CLI output as fallback and say which evidence was unavailable.
The self-improving QA agent for software teams. A test harness with memory. Write tests in natural language for web and mobile. agent-qa learns from every run, adapts to UI changes, and catches regressions before you ship.
Repo: vostride/agent-qa
Other skills on agent-qa.
- /agent-qa-authoring
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.
Open skill - /agent-qa-debug-fix
Use after an agent-qa run has failed and you need to debug, patch, and verify the issue using MCP evidence, logs, artifacts, and local code changes instead of generated fix suggestions.
Open skill - /agent-qa-authoring
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.
Open skill - /agent-qa-debug-fix
Use after an agent-qa run has failed and you need to debug, patch, and verify the issue using MCP evidence, logs, artifacts, and local code changes instead of generated fix suggestions.
Open skill