sickn33/agentic-awesome-skills / plugins/agentic-awesome-skills-claude/skills/agent-qa-result-triage
agent-qa-result-triage
VerifiedTriage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.
Agent QA Result Triage
Overview
Classify a failed Agent QA run from its recorded evidence instead of guessing. Inspect the run, steps, artifacts, and logs; choose one fixed category; and return confidence, likely ownership, and the next evidence-backed action.
When to Use
- Investigating a failed or interrupted Agent QA run.
- Inspecting run artifacts, step results, or execution logs.
- Comparing recent related runs for recurring failure patterns.
- Deciding whether a failure belongs to a test, product, hook, browser/mobile runtime, or infrastructure owner.
Workflow
- Start with
agent_qa_get_runfor run status, suite child context, steps, and attempts. - Fetch evidence before deciding:
agent_qa_get_run_artifactagent_qa_get_run_stepsagent_qa_get_run_logsagent_qa_get_run_execution_logs
- Call
agent_qa_classify_failureand use its category as the default classification unless stronger evidence contradicts it. - Compare recent related runs when they are available in the classifier output.
- Return a concise triage result: category, confidence, evidence, likely fix area, and next action.
- For code changes, switch to
agent-qa-debug-fixafter triage is complete.
Categories
Use exactly one category from references/triage-categories.md:
timeoutappium_startupbrowser_disconnectelement_not_foundassertion_failurehook_failureinfrastructureunknown_failure
Evidence Rules
- Quote or summarize concrete artifact, log, or step evidence.
- Mention missing artifact sections when they limit confidence.
- Do not invent screenshots, videos, logs, or memory context that MCP did not return.
- If MCP is unavailable, use dashboard REST APIs or Agent QA CLI output as a fallback and state which evidence was unavailable.
- Redact credentials, session tokens, personal data, and unrelated application content from the report.
Example
{
"category": "element_not_found",
"confidence": "high",
"evidence": ["Step 4 could not resolve the described checkout button"],
"likely_fix_area": "test definition or changed product UI",
"next_action": "Inspect the captured UI context, then compare the current checkout screen"
}
Limitations
- Classification is only as reliable as the retained run artifacts and logs.
- A failure category identifies the most likely failure surface; it does not prove root cause.
- Missing screenshots, DOM/accessibility context, device logs, or prior runs must lower confidence.
- This skill does not modify tests or application code; use
agent-qa-debug-fixfor an authorized repair.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |