skills.rest
battyejp
battyejpCOMMUNITY
Explore all skills by this author →
GitHub

dev-browser

Automate browser interactions with persistent sessions using Node and Playwright.

Updated Jan 14, 2026
Search Tags:#automation#screenshots#scripting#playwright#browser#web-scraping#persistent-state
One-click install
npx skills add https://github.com/battyejp/amp-ralph-api --skill dev-browser-battyejp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-browser
Source: https://github.com/battyejp/amp-ralph-api/tree/main/skills/dev-browser
Command: npx skills add https://github.com/battyejp/amp-ralph-api --skill dev-browser-battyejp

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables reliable browser automation by maintaining a persistent page state across script executions, eliminating repeated login and setup steps for repetitive web tasks.

Core Features & Use Cases

  • Persistent browser context across runs to keep login sessions and storage.
  • Script-driven, single-action tasks (navigate, click, fill, screenshot) that can be composed into larger workflows.
  • Use cases include automated QA workflows, data scraping from web apps, form automation, and end-to-end testing.

Quick Start

Use the dev-browser skill to open a site, perform a login, and capture a screenshot of the landing page.

Frequently Asked Questions about dev-browser

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

FAQPage Schema
How do I keep browser state and login sessions persistent across Playwright script executions?▼

You maintain persistent browser state across Playwright script executions by using a persistent browser profile, which keeps login sessions and storage intact to streamline repeated web automation tasks.

How do I automate form filling and screenshots across multiple web pages?▼

You automate form filling and screenshots across multiple pages by composing script-driven, single-action tasks into larger workflows, applying navigation, clicking, and data scraping actions across sessions.

Do I need a local Node and Playwright setup to run browser automation tasks?▼

Yes, a local Node and Playwright setup is required to run browser automation tasks, providing the server tooling and scripts needed to manage pages and execute actions reliably.

What is the best way to automate QA workflows and data scraping for web apps?▼

The best way to automate QA workflows and data scraping for web apps is maintaining a persistent page state across runs, allowing reliable navigation and data extraction without repeated login steps.

Why does my web scraping script require logging in every time it runs?▼

Web scraping scripts require logging in every run because they lack a persistent browser context; maintaining a persistent page state across executions eliminates repeated login and setup steps.

Related Skills

Explore More Software Engineering Skills→
ZhanlinCuiZhanlinCui
178

webapp-testing

Test local web applications with Playwright and capture UI artifacts.

Community
Intermediate
mkrlabsmkrlabs

qa-report-contract

Generate structured QA verdicts and metrics for validation workflows.

Official
Advanced
anthropicsanthropics
167.2k

webapp-testing

Automate local web application testing with Playwright and multi-server orchestration.

Official
Intermediate
hathbangerhathbanger

agent-browser

Automate web navigation and interaction via a headless browser CLI.

Community
Intermediate