uat-run

Orchestrate UAT pre-checks and manual verification from markdown checklists.

1|Updated Apr 3, 2026

Search Tags:#automation #workflow #testing #quality assurance #bug tracking #uat

Ready to run

npx skills add https://github.com/owebboy/maestro --skill uat-run

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: uat-run
Source: https://github.com/owebboy/maestro/tree/main/skills/uat-run
Command: npx skills add https://github.com/owebboy/maestro --skill uat-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes the friction from User Acceptance Testing by providing an interactive, guided walkthrough that automates pre-checks and standardizes the capture of test failures.

Core Features & Use Cases

Automated Pre-Validation: Executes SQL queries and shell commands to verify prerequisites before manual testing begins.
Guided Walkthrough: Presents test sections one by one, allowing for efficient, focused manual verification.
Failure Capture: Standardizes the logging of bugs and issues directly into the project's inbox with automated priority and type inference.

Quick Start

Invoke the uat-run skill to begin the interactive testing process for the most recent UAT checklist file.

Frequently Asked Questions about uat-run

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

FAQPage Schema

How do I automate User Acceptance Testing pre-checks before manual verification?▼

User Acceptance Testing pre-checks are automated by executing SQL queries and shell commands to validate system prerequisites before manual testing begins. This interactive proctor orchestrates these non-destructive checks against a project-specific markdown checklist to verify environment readiness.

What is the best way to structure a UAT checklist for automated validation?▼

A UAT checklist for automated validation should be structured as a project-specific markdown file. The interactive proctor parses this markdown to orchestrate automated pre-checks and present test sections sequentially for guided manual verification.

How does guided User Acceptance Testing handle bug tracking and failure capture?▼

Guided User Acceptance Testing handles bug tracking by standardizing the capture of test failures directly into the project's inbox. During the interactive walkthrough, the proctor logs identified defects with automated priority and type inference for seamless tracking.

Do I need a local database MCP tool to run interactive UAT workflows?▼

Yes, a local database MCP tool and shell environment are required to run interactive UAT workflows. These integrations enable the proctor to execute non-destructive SQL queries and shell commands during the automated pre-validation phase.

Can I execute SQL queries during User Acceptance Testing without damaging production data?▼

Yes, you can execute SQL queries during User Acceptance Testing without damaging data because the proctor performs only non-destructive validation tasks. It leverages local database MCP tools to verify prerequisites safely before manual testing begins.

Why should I use an interactive UAT proctor instead of manual quality assurance checklists?▼

An interactive UAT proctor removes friction from quality assurance by automating pre-checks and standardizing failure capture, whereas manual checklists lack automated validation. It orchestrates structured verification workflows and logs bugs with inferred priority directly into your project inbox.