skills.rest
Intension-us
Intension-usOFFICIAL
Explore all skills by this author →
GitHub

browse

Drive headless browsers to load URLs, interact with elements, and verify page state.

Updated Apr 3, 2026
Search Tags:#screenshots#diff#playwright#web-testing#browse#headless-browser#qa-automation
One-click install
npx skills add https://github.com/Intension-us/attention-diagnostic --skill browse-intension-us
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/Intension-us/attention-diagnostic/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/Intension-us/attention-diagnostic --skill browse-intension-us

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates QA browser testing by driving a headless browser to load URLs, interact with elements, verify page state, and capture evidence such as annotated screenshots and diffs.

Core Features & Use Cases

  • Headless QA automation: load pages, interact with forms and dialogs, take annotated screenshots, and verify UI state across deployments.
  • Visual diffs and responsive checks: compare before/after states and test layouts on multiple viewports.
  • Use cases: test a feature release, dogfood a user flow, or file a bug with concrete evidence.

Quick Start

Open a URL with browse and verify the page loads and key elements appear.

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 feature releases?▼

Automate headless browser QA testing by driving a Playwright-compatible browser to load URLs, interact with elements, verify page state, and capture annotated screenshots as deployment verification evidence.

Can I capture visual diffs and responsive layout checks across multiple viewports?▼

Visual diffs and responsive checks are supported by comparing before and after states across multiple viewports, allowing you to verify UI state and layout consistency during feature testing.

Do I need Playwright-compatible browsers installed to run web-testing automation?▼

Playwright-compatible browsers are required in the environment to run this web-testing automation, which drives headless browser steps for navigation, interaction, and state assertions.

What's the best way to reproduce a bug with concrete evidence using a headless browser?▼

Reproduce a bug with concrete evidence by driving a headless browser through the user flow, interacting with forms and dialogs, and capturing annotated screenshots of the resulting page state.

Does headless QA automation support state assertions and element interaction?▼

Headless QA automation supports navigation, element interaction, and state assertions to verify UI state, dogfood user flows, and test feature releases across deployments.

Related Skills

Explore More Software Engineering Skills→
agatxagatx
5

setup-browser-cookies

Import and decrypt browser cookies into a Playwright headless session.

Community
Advanced
JaykaijackJaykaijack

browse

Automate headless Chromium browsing and UI verification with screenshots and diffs.

Community
Advanced
RxFitRxFit

browse

Automate headless browser interactions to verify web pages and test user flows.

Community
Advanced
JosiahSiegelJosiahSiegel
51

powershell-master

Automate cross-platform tasks with PowerShell 7+ scripts.

Community
Advanced