skills.rest
az9713
az9713COMMUNITY
Explore all skills by this author →
GitHub

browse

Navigate websites, interact with elements, and capture screenshots in a headless browser.

2|Updated Apr 5, 2026
Search Tags:#QA#browser#headless#QA testing#site dogfooding
One-click install
npx skills add https://github.com/az9713/paperclip-gstack-company --skill browse-az9713
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/az9713/paperclip-gstack-company/tree/main/gstack/browse
Command: npx skills add https://github.com/az9713/paperclip-gstack-company --skill browse-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a headless browser for QA testing and site dogfooding, allowing users to navigate websites, interact with elements, verify page states, and take screenshots efficiently.

Core Features & Use Cases

  • Headless Browser: Accesses websites without a graphical user interface, enabling automated testing and analysis.
  • Page Navigation and Interaction: Navigates to URLs, clicks elements, fills forms, and handles dialogs.
  • Page State Verification: Checks for correct element visibility, responsive layouts, and form submissions.
  • Screenshot and Logging: Captures screenshots and logs for debugging and verification purposes.
  • Use Case: When you need to test a new feature, verify a deployment, or file a bug with evidence.

Quick Start

To navigate to a URL, use the command: goto <url>

Frequently Asked Questions about browse

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

FAQPage Schema
How do I run headless browser QA testing for site dogfooding?▼

Headless browser QA testing for site dogfooding runs without a graphical interface to automate website navigation, element interaction, page state verification, and screenshot capture for deployment validation.

What is the best way to verify page states and capture screenshots during deployment verification?▼

The best way to verify page states during deployment verification is using a headless browser to check element visibility, validate responsive layouts, confirm form submissions, and capture screenshots for evidence.

Can I use a headless browser to automate filling forms and clicking elements?▼

Yes, you can use a headless browser to automate clicking elements, filling forms, navigating to URLs, and handling dialogs for comprehensive automated testing and debugging workflows.

Does headless browser testing work for automated feature testing and bug filing?▼

Headless browser testing works for automated feature testing and bug filing by navigating websites, verifying correct element visibility, and capturing screenshots with logs to provide concrete debugging evidence.

How do I navigate to a URL to start automated website testing?▼

To start automated website testing, navigate to a URL using the `goto <url>` command, which instructs the headless browser to access the target page for subsequent interaction and state verification.

Why use a headless browser instead of a standard browser for QA testing?▼

A headless browser is used instead of a standard browser for QA testing because it operates without a graphical user interface, enabling faster automated testing, efficient site dogfooding, and streamlined debugging.

Related Skills

Explore More Software Engineering Skills→
jonkikyjonkiky

browse

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

Community
Advanced
AztecProtocolAztecProtocol
449

debug-e2e

Coordinates interactive debugging sessions for failed end-to-end CI tests via subagents.

Official
Advanced
micaelmaltamicaelmalta
1

ci-cd

Configure CI/CD pipelines across GitHub Actions, GitLab CI, Jenkins, and CircleCI.

Community
Basic
hpurihpuri

Browser Tester

Run E2E visual and interactive tests on ADK agents in a browser.

Community
Advanced