browse

Automate QA workflows with a programmable headless browser.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/lendtrain/complete-pipeline --skill browse-lendtrain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/lendtrain/complete-pipeline/tree/main/skills/browse
Command: npx skills add https://github.com/lendtrain/complete-pipeline --skill browse-lendtrain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly validate web features and deployments by providing a fast, programmable headless browser to automate QA tasks, capture evidence, and dogfood user flows.

Core Features & Use Cases

  • Automated UI testing: navigate pages, interact with elements, and verify states.
  • Visual evidence: diff results and annotated screenshots to document changes.
  • Responsive validation: test layouts across mobile, tablet, and desktop.
  • Form and dialog testing: automate form inputs and dialog handling for consistent bug reproduction.

Quick Start

Launch the skill to spin up a local headless browser and begin automated QA checks.

Frequently Asked Questions about browse

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

FAQPage Schema
What is a headless browser used for in QA testing?

A headless browser executes web pages without a graphical interface to automate QA testing. It validates web deployments by navigating pages, interacting with elements, and verifying state to streamline feature validation in development pipelines.

How do I automate UI testing and capture annotated screenshots?

Automate UI testing by scripting a headless browser to navigate pages, input forms, and verify states. Capture annotated screenshots and visual diffs during execution to document changes and log evidence for deployments.

Can I test responsive layouts across mobile and desktop viewports?

Yes, responsive validation tests layouts across mobile, tablet, and desktop viewports. The headless browser programmatically adjusts viewport dimensions to verify responsive design behavior and detect layout regressions.

Does this headless browser support form inputs and dialog handling for bug reproduction?

Yes, it supports form and dialog testing by automating form inputs and dialog handling. This enables consistent bug reproduction by executing deterministic scripts that interact with web page elements and verify system states.

What's the best way to integrate automated QA checks into continuous integration workflows?

Integrate automated QA into continuous integration workflows by running deterministic headless browser scripts. Execute navigation, state verification, and visual diff checks to generate repeatable tests and accessibility data for deployments.

Why use a programmable headless browser instead of manual web testing?

A programmable headless browser provides reliable, repeatable tests by automating user flows and capturing evidence. It replaces manual testing with deterministic scripting, enabling rapid visual diffs and accessibility data generation for pipeline validation.