skills.rest
norbert-pap
norbert-papCOMMUNITY
Explore all skills by this author →
GitHub

browse

Automates browser-based QA tasks with a configurable, headless Chromium runner.

Updated Apr 7, 2026
Search Tags:#automation#playwright#browse#qa-testing#headless-chromium
One-click install
npx skills add https://github.com/norbert-pap/claudebert --skill browse-norbert-pap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/norbert-pap/claudebert/tree/main/browse
Command: npx skills add https://github.com/norbert-pap/claudebert --skill browse-norbert-pap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates fast, deterministic browser-based QA tasks so you can test features, verify deployments, and collect evidence without repetitive manual clicks.

Core Features & Use Cases

  • Navigate to URLs, interact with elements, verify page state, and persist session state for repeatable tests.
  • Take annotated screenshots, diff changes, and verify responsive layouts across breakpoints.
  • Handle dialogs and element-state assertions to produce evidence for bug reports.

Quick Start

Launch the skill and run a simple QA flow against a URL to validate a user path.

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 with Playwright?▼

You can automate headless browser QA testing by using a Playwright-based runner to navigate URLs, interact with elements, and verify page state without manual clicks. This skill handles deterministic test execution and collects evidence.

Can I take annotated screenshots and diff layout changes during automated testing?▼

Yes, you can take annotated screenshots and diff visual changes during automated testing. The skill captures screenshots, compares differences, and verifies responsive layouts across multiple breakpoints to produce bug report evidence.

Do I need a local Playwright runtime to run headless Chromium workflows?▼

Yes, a local Playwright-based runtime is required to execute headless Chromium workflows. The skill relies on this environment to automate navigation, interaction, and state verification tasks driven by frontmatter configuration.

What is the best way to verify deployments across responsive breakpoints without manual checks?▼

The best way to verify deployments without manual checks is running automated headless browser sessions. This skill navigates target URLs, asserts element states, handles dialogs, and executes responsive checks across breakpoints.

Can I persist session state for repeatable browser automation tests?▼

Yes, you can persist session state for repeatable browser automation tests. The skill supports maintaining state across navigation and interaction steps, enabling consistent and deterministic QA workflows against deployments.

How does frontmatter configuration drive automated QA workflows?▼

Frontmatter configuration drives automated QA workflows by loading settings from SKILL.md. This file directs the headless Chromium runner, specifying navigation targets, interaction scripts, and references for test execution.

Related Skills

Explore More Software Engineering Skills→
I194I194
9

browse

Automate Playwright/Chromium browser interactions and verify page states.

Community
Advanced
rahmanayonrahmanayon

browse

Automate QA browser testing by navigating URLs, interacting with elements, and capturing annotated screenshots.

Community
Advanced
GrassHopper42GrassHopper42

ios-fix

Detect, repair, and verify iOS bugs in CI/CD pipelines.

Community
Advanced
SoSoBurnerSoSoBurner

browse

Automate headless browser actions for QA testing using Playwright.

Community
Advanced