qa-preflight

Verify QA audit environment readiness before browser-driven audits.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-preflight
Source: https://github.com/Luqman-Ud-Din/blackbox-qa-agent/tree/main/skills/qa-preflight
Command: npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted time and failed audits by verifying that the target app, browser bridge, runtime, and required security settings are ready before the QA workflow starts.

Core Features & Use Cases

  • Fast URL health checks: Confirms the application is reachable before any expensive browser work begins.
  • Browser bridge detection and recovery: Detects whether Playwright MCP is available, auto-installs it when missing, and guides the user through restart requirements.
  • Environment validation: Checks Node, browser readiness, secrets handling, jq, and Azure DevOps access only when the chosen run actually needs them.
  • Use case: A QA engineer can run a preflight step against a local or staging app to catch downtime, missing browser support, or misconfigured credentials before launching a full audit.

Quick Start

Ask the agent to run the preflight checks for the current QA audit setup and report any blocking environment or connectivity issues.

Frequently Asked Questions about qa-preflight

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

FAQPage Schema
How do I check if my Playwright environment is ready before running a browser audit?

Preflight checks verify whether the Playwright MCP browser bridge is available, automatically installs it if missing, and guides you through required restarts to ensure your browser audit environment is fully configured.

What environment checks are required for Azure DevOps browser automation audits?

Azure DevOps browser automation audits require conditional preflight checks for target URL health, jq availability, configured secrets, and valid Personal Access Token (PAT) validation before the workflow can safely execute.

Why does my QA audit fail before it starts running?

QA audits often fail due to unreachable target URLs, missing Playwright MCP browser binaries, unsupported Node runtimes, or misconfigured credentials, which preflight checks identify and help you resolve before execution.

Do I need to configure secrets for a dry run browser audit?

No, preflight checks skip irrelevant steps like secrets validation and Azure DevOps access checks for dry runs or unsupported bridge modes, ensuring only necessary environment configurations are enforced.

How do I validate target URL health for Node browser automation?

Perform a fast preflight URL health check to confirm your target application is reachable and properly configured before initiating any expensive Playwright browser-driven automation work.

Can I use preflight checks for local staging app QA testing?

Yes, QA engineers can run preflight validation against local or staging apps to catch downtime, missing browser support, and misconfigured credentials before launching a full audit workflow.