pavilio-qa-agent

Runs browser-based acceptance criteria checks with screenshot evidence and structured run reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual QA against acceptance criteria is slow and hard to audit: testers must walk flows in a browser, remember to capture evidence, and write up results by hand. This Skill automates that pass by driving a browser through a scenario, capturing a screenshot before every check, and persisting a self-contained run folder with markdown and JSON reports. ## Core Features & Use Cases - Acceptance-criteria-driven runs: Walks a numbered list of criteria in order, evaluates each as passed or failed, and records notes plus an evidence screenshot per criterion. - Self-contained run artifacts: Creates projects/<project>/qa/runs/<timestamp>-<env>-<ticket>-<label>/ containing run.md, run.json, and a screenshots/ folder. - Per-project configuration: Resolves envs, accounts, saved AC files, flows, and helper overrides from projects/<project>/qa/ with shared fallbacks. - Use Case: Before signing off on ticket ACCM-123, ask the agent to verify its acceptance criteria on the local environment; it logs in, walks the flow, screenshots each check, and produces a pass/fail report you can attach to the ticket. ## Quick Start Run /pavilio-qa-agent with --project=myapp --env=local --ticket=ACCM-123 and paste the start URL plus the numbered acceptance criteria to verify.

Frequently Asked Questions about pavilio-qa-agent

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

FAQPage Schema
How do I run automated QA against acceptance criteria in a browser?▼

Invoke /pavilio-qa-agent with a project, environment, and start URL, then supply a numbered list of acceptance criteria. The agent walks the scenario with agent-browser, screenshots before every check, and marks each criterion passed or failed in a run report.

How do I verify a Jira ticket with screenshot evidence?▼

Pass --ticket=<ID> to the QA agent; it reuses any saved acceptance criteria file matching that ticket under projects/<project>/qa/ac/ or saves new criteria you paste. Each criterion gets an evidence screenshot stored in the run folder.

Can I use project-specific accounts and environments for QA runs?▼

Yes. The agent reads projects/<project>/qa/accounts.yml and env configuration before asking for inputs, preferring accounts not flagged blocked, obsolete, or sensitive. Project-local helpers under qa/lib/ override the shared ones when needed.

What artifacts does a browser QA run produce?▼

Each run creates a folder under projects/<project>/qa/runs/ named by timestamp, env, ticket, and label. It contains run.md with inline screenshots per checkpoint, machine-readable run.json, and a screenshots/ directory.

What are the safety limits of automated browser QA?▼

The agent never places orders or submits payment information, and it always writes run artifacts and finalizes the run even on failure or block. If the browser session cannot start, it reports which environment URL was unreachable.