maestro-qa-report

Runs report-only Maestro QA flows on mobile simulators and generates severity-classified findings.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill maestro-qa-report-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maestro-qa-report
Source: https://github.com/gmackie/agent-skills/tree/main/skills/maestro-qa-report
Command: npx skills add https://github.com/gmackie/agent-skills --skill maestro-qa-report-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires maestro, bash, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve? Mobile QA on React Native and Expo apps often produces vague, unreproducible bug reports or gets mixed up with code fixes. This Skill runs Maestro flows on a local simulator or emulator as a strictly report-only pass, capturing screenshots, logs, and structured reports so failures are documented with exact repro steps and severity. ## Core Features & Use Cases - Prerequisite Verification: Checks that the Maestro CLI, a running simulator or emulator, and flow files exist before executing anything. - Artifact and Report Generation: Runs flows with explicit output directories, HTML or JUnit report formats, optional tag filtering, and debug output capture via a bundled bash helper script. - Severity-Classified Findings: Classifies each verified failure as blocker, major, minor, or cosmetic with exact flow steps, expected vs actual behavior, and suspected ownership using a report template. - Use Case: A developer asks for a QA report on login and onboarding flows before a release. The Skill verifies the environment, runs the targeted Maestro flows, inspects screenshots and logs, and produces a concise report without touching app code. ## Quick Start Run Maestro QA on the login and onboarding flows in this repo and give me a severity-classified report with repro steps and artifact paths.

Frequently Asked Questions about maestro-qa-report

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

FAQPage Schema
How do I run Maestro tests and generate an HTML report?▼

Run maestro test with the --format html-detailed flag, an --output report file path, and --test-output-dir for artifacts. The bundled helper script wraps these flags and validates prerequisites like the Maestro CLI and flow files first.

How to filter Maestro flows by tags?▼

Pass --include-tags with a tag value such as smoke to the Maestro test command or the helper script. This narrows the run to only flows matching those tags, which is useful for running short smoke suites before larger ones.

Can I use Maestro QA with Expo Go apps?▼

Expo Go is not a reliable QA target for serious testing. Use an Expo development build or a dedicated preview or test build instead, since many issues depend on native code that Expo Go does not include.

Why does my Maestro run fail before any flow executes?▼

Common causes are the Maestro CLI not being installed or on PATH, no running simulator or emulator, or a missing flow path. Verify each prerequisite separately so environment setup issues are not mistaken for app bugs.

Does this QA approach fix the bugs it finds?▼

No, it is strictly report-only. Failures are documented with severity, repro steps, artifacts, and suspected ownership, then escalated as a clean report rather than being fixed during the QA pass.