qa-team

Orchestrate multi-agent QA testing with tester, developer, and reviewer roles.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SalesTeamToolbox/frood --skill qa-team-salesteamtoolbox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-team
Source: https://github.com/SalesTeamToolbox/frood/tree/main/skills/builtins/qa-team
Command: npx skills add https://github.com/SalesTeamToolbox/frood --skill qa-team-salesteamtoolbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA Team prevents missed bugs by coordinating multiple perspectives—testing, fixing, and final verification—when a single pass is not enough for complex applications.

Core Features & Use Cases

  • Fan-out QA coverage: orchestrates a comprehensive test run across smoke checks, user-flow testing, log inspection, and visual page review.
  • Bug triage and iterative fixes: routes findings to a developer role that diagnoses root causes, applies fixes, restarts the app, and re-verifies health.
  • Final readiness validation: executes clean smoke testing, rechecks key pages, confirms logs are clean, and generates a final QA report with a deployment-readiness score.

Use case example: You need independent verification for an app with multiple pages, backend endpoints, and user flows that was created by a different agent; QA Team will test the full surface area, drive fixes, and produce a readiness score.

Quick Start

Use the qa-team skill to run a multi-agent QA workflow for your application at http://localhost:<port> by specifying the objective with app_id and port.

Frequently Asked Questions about qa-team

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multi-agent QA testing for application verification?▼

Multi-agent QA testing coordinates tester, developer, and reviewer roles to execute smoke tests, user-flow coverage, log checks, and visual verification across your application's routes and APIs for thorough deployment readiness validation.

What is the best way to triage bugs found during smoke testing?▼

Bug triage routes smoke test findings to a developer role that diagnoses root causes, applies iterative fixes, restarts the app, and re-verifies health before proceeding to final readiness validation.

Can I use automated QA workflows for complex apps with multiple routes and APIs?▼

Yes, automated QA workflows apply to complex apps with multiple routes and APIs by orchestrating smoke checks, user-flow testing, log inspection, and visual page review, followed by iterative remediation and final readiness scoring.

How do I get a deployment readiness score for my local application?▼

A deployment readiness score is generated after executing clean smoke testing, rechecking key pages, and confirming logs are clean. Run the QA workflow on your app at http://localhost:<port> with a specified app_id and port to get the final report.

When should I use a multi-agent QA workflow instead of a single test pass?▼

Use a multi-agent QA workflow when a single test pass is insufficient for complex applications with multiple pages, backend endpoints, and user flows, requiring coordinated testing, iterative fixing, and final verification to prevent missed bugs.