browse

Automate web application navigation, interaction, and verification with a headless browser.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/Manzueti/cyberdart --skill browse-manzueti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/Manzueti/cyberdart/tree/main/browse
Command: npx skills add https://github.com/Manzueti/cyberdart --skill browse-manzueti

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a headless browser for QA testing and site dogfooding, enabling automated navigation, interaction, and verification of web applications.

Core Features & Use Cases

  • Automated Navigation: Navigate any URL and interact with web elements.
  • Verification: Verify page state, take screenshots, and diff before/after actions.
  • Use Case: Use this Skill to test a new feature, verify a deployment, or file a bug with evidence of the issue.

Quick Start

Run the browse skill to navigate to the URL 'https://example.com'.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate web application testing with a headless browser?

Automated headless browser testing enables navigation, interaction, and verification of web applications without a visible UI. This Skill uses Playwright to drive a headless browser environment for site dogfooding and QA workflows.

How do I take screenshots and diff before and after actions during QA testing?

Screenshot diffing during QA testing captures the page state before and after specific actions to verify visual changes. This Skill enables automated verification by taking screenshots and comparing them to detect UI regressions.

Do I need Playwright installed to run headless browser tests?

Yes, Playwright is required to run headless browser tests with this Skill. It serves as the underlying automation framework that drives browser navigation, interaction, and verification within your software development workflow.

What is site dogfooding and when do I need a headless browser for it?

Site dogfooding is internally testing your own web application to find issues before deployment. You need a headless browser when you want to automate this navigation and verification process continuously without manual UI interaction.

Can I use this Skill to verify a new deployment and automatically file a bug?

Yes, you can verify a new deployment by navigating to URLs and interacting with web elements automatically. This Skill helps file a bug with evidence by capturing screenshots and verifying the page state of your web application.