dev-browser

Automate browser interactions while preserving page state across script executions.

Updated Mar 6, 2026

Search Tags:#automation #scripting #playwright #web-testing #browser #stateful

Ready to run

npx skills add https://github.com/decebal/decebal-claude-skills --skill dev-browser-decebal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-browser
Source: https://github.com/decebal/decebal-claude-skills/tree/main/skills/dev-browser
Command: npx skills add https://github.com/decebal/decebal-claude-skills --skill dev-browser-decebal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates browser interactions while preserving page state across script executions, reducing repetitive manual steps and enabling more reliable workflows.

Core Features & Use Cases

Small, focused scripts that perform one action at a time (navigate, click, fill, wait, collect data).
Stateful pages across sessions and scripts, enabling multi-step workflows without reloading context.
Supports standalone and extension modes, with a clear workflow to start/attach to a browser.

Quick Start

Launch the standalone server and start writing small scripts to automate common browser tasks.

Frequently Asked Questions about dev-browser

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

FAQPage Schema

How do I automate browser workflows while preserving page state across script executions?▼

Stateful browser automation preserves page state across script executions by using a lightweight client-server flow, enabling small focused scripts to progressively build multi-step workflows without reloading context or losing session data.

Can I run Playwright web-testing scripts without losing my page session every time?▼

Yes, stateful web-testing scripts can attach to a persistent browser session via standalone or extension modes, allowing you to execute sequential actions like clicking and filling forms while maintaining the exact page state between runs.

What is the best way to build end-to-end browser automation scripts for scraping data?▼

The best way to build scraping workflows is using small, focused scripts that perform one action at a time, such as navigating to URLs and collecting data, which progressively combine into reusable end-to-end browser automation sequences.

Does this browser automation tool support taking screenshots during multi-step web workflows?▼

Yes, the browser automation tool supports taking screenshots as one of its core actions, alongside navigating, clicking, filling forms, and waiting, making it suitable for testing web apps and automating visual verification workflows.

How do I start a stateful browser automation server for scripting tasks?▼

To start stateful browser automation, launch the standalone server and begin writing small scripts that perform individual actions like navigating to URLs or interacting with elements to progressively build reusable workflows.

Why does my browser automation script lose context when navigating between multiple pages?▼

Standard scripts lose context because they reload state on each execution, but stateful browser automation solves this by preserving page state across sessions, allowing multi-step workflows to navigate and interact without losing prior context.