browse

Drive a headless browser to navigate pages, interact with elements, and capture evidence.

1|2|Updated Jan 4, 2024
One-click install
npx skills add https://github.com/NaKMiers/Port4lio --skill browse-nakmiers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/NaKMiers/Port4lio/tree/main/.agents/skills/browse
Command: npx skills add https://github.com/NaKMiers/Port4lio --skill browse-nakmiers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve?

Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states.

Core Features & Use Cases

  • Automates QA flows by driving a headless browser to interact with pages, capture evidence, and compare results across deployments.
  • Supports deterministic task execution, responsive testing, form interactions, and dialog handling for bug reproduction and feature verification.
  • Use cases include feature verification, deployment checks, bug reproduction with evidence, and ongoing QA workflows in modern web apps.

Quick Start

Run a QA session by launching the browse skill, navigating to a URL, performing actions, and capturing a screenshot to document results.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate headless browser QA testing for web app deployments?

Automate headless browser QA testing by driving a browser to navigate URLs, interact with elements, and capture screenshots. This verifies deployments and reproduces bugs by diffing page states before and after actions.

Can I capture screenshots and evidence during bug reproduction with Playwright?

Yes, you can capture annotated screenshots and evidence during bug reproduction. The automation flow drives a headless browser to interact with pages and document results for feature verification.

What is headless browser dogfooding and when do I need it for modern web apps?

Headless browser dogfooding is executing deterministic QA flows to test your own web apps before release. You need it for ongoing QA workflows, deployment verification, and feature checks on modern web platforms.

Does this QA automation tool support responsive layout testing and form interactions?

Yes, the QA automation tool supports responsive layout testing, form interactions, and dialog handling. It drives a headless browser to check responsive designs, test forms and uploads, and handle dialogs.

Do I need Playwright installed to run headless browser automation scripts?

Yes, you need Playwright installed as a dependency to run headless browser automation scripts. The skill requires Playwright for browser automation to execute end-to-end QA flows and deployment verification.

What's the best way to verify page states and diff results across deployments?

The best way to verify page states is driving a headless browser to navigate pages, interact with elements, and diff results across deployments. This deterministic task execution targets deployment verification and bug reproduction.