skills.rest
onlypfachi
onlypfachiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

browse

Drive a persistent headless browser to automate QA testing and site dogfooding.

Updated Mar 19, 2026
Search Tags:#automation#testing#qa#playwright#browser#headless#browse
One-click install
npx skills add https://github.com/onlypfachi/chief --skill browse-onlypfachi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/onlypfachi/chief/tree/main/browse
Command: npx skills add https://github.com/onlypfachi/chief --skill browse-onlypfachi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates QA testing and site dogfooding by driving a persistent headless browser so you can reproduce flows reliably.

Core Features & Use Cases

  • Deterministic browser automation: goto, fill, click, type, and more, across sessions and tabs.
  • Evidence collection: capture screenshots, console logs, network traces, and state diffs for bug reports.
  • Stateful sessions: preserve cookies, localStorage, and tabs across commands and handoffs for realistic workflows.

Quick Start

Start the Chief browse server and issue commands from your agent to run QA tasks end-to-end.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate QA testing with a headless browser to reproduce user flows reliably?▼

Automating QA testing with a headless browser involves driving persistent sessions to execute scripted interactions like goto, fill, and click. This approach preserves cookies and local state across commands, ensuring reliable reproduction of user flows for deployment validation.

How do I capture network traces and console logs for bug reports during browser automation?▼

Capturing network traces and console logs during browser automation is achieved by instrumenting deterministic execution with rich evidence collection. You gather screenshots, console logs, and state diffs directly from the headless session to document exact failure points.

Can I preserve browser state and tabs across multiple scripted interactions for site dogfooding?▼

Yes, you can preserve browser state and tabs across multiple scripted interactions for site dogfooding. Stateful sessions maintain cookies, local storage, and open tabs across sequential commands and handoffs, enabling realistic and continuous workflow verification.

What is the best way to verify deployments across multiple URLs with deterministic browser automation?▼

The best way to verify deployments across multiple URLs is using frontmatter-driven discovery and deterministic browser automation. This method scripts stateful interactions across sessions, capturing screenshots and state diffs to validate user flows reliably.

Does headless browser automation work for collecting evidence across stateful sessions?▼

Yes, headless browser automation works for collecting evidence across stateful sessions. By driving a persistent browser, you capture screenshots, console logs, network traces, and state diffs across different URLs and scripted interactions for bug reports.

Related Skills

Explore More Software Engineering Skills→
jonkikyjonkiky

browse

Automate QA testing with a persistent headless browser for web interactions.

Community
Advanced
proffesor-for-testingproffesor-for-testing
436

bug-reporting-excellence

Create structured bug reports with reproduction steps and environment details.

Community
Advanced
andrew-t-jamesandrew-t-james

setup-browser-cookies

Import browser cookies into a headless session for authenticated testing.

Community
Intermediate
abustamamabustamam

gstack

Automate browser-based QA testing with Playwright and diff-enabled verification.

Community
Advanced