skills.rest
DJJones66
DJJones66COMMUNITY
Explore all skills by this author →
GitHub

dev-browser

Control a browser with persistent page state across script executions.

Updated Jan 22, 2026
Search Tags:#automation#playwright#scripts#browser#stateful#web-automation
One-click install
npx skills add https://github.com/DJJones66/BrainDrive-Forge --skill dev-browser-djjones66
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-browser
Source: https://github.com/DJJones66/BrainDrive-Forge/tree/main/skills/dev-browser
Command: npx skills add https://github.com/DJJones66/BrainDrive-Forge --skill dev-browser-djjones66

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser automation with persistent page state reduces the need to recreate sessions and re-navigate between runs, enabling more reliable and efficient automation.

Core Features & Use Cases

  • Persisted browser context that keeps cookies, localStorage, and session data between runs.
  • Standalone mode and extension mode to accommodate different user environments.
  • Script-based actions (navigate, click, fill, screenshot, ARIA snapshots) that can be composed into end-to-end workflows.

Quick Start

Start by writing a small automation script that opens a page, performs a sequence of actions, and observes results.

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 session state persistent across multiple automation script runs?▼

Persistent browser automation preserves page state across script executions by retaining cookies, localStorage, and session data between runs, eliminating the need to recreate sessions and re-navigate to URLs each time.

What is the difference between standalone mode and extension mode for web automation?▼

Standalone mode implements a launchable browser context via a standalone server, while extension mode uses a Chrome extension bridge, allowing web automation to accommodate different user environments and continuity requirements.

How do I automate filling forms and taking screenshots in workflows requiring continuity?▼

You can compose script-based actions like navigate, click, fill, screenshot, and ARIA snapshots into end-to-end workflows, automatically controlling the browser while preserving page state for reliable automation.

Does Playwright support stateful browser automation with preserved cookies and localStorage?▼

Yes, stateful web automation with Playwright supports a persisted browser context that keeps cookies, localStorage, and session data between runs, enabling reliable automation without recreating sessions.

Can I use this browser automation approach for scraping data and testing web apps?▼

Yes, persistent browser automation is ideal for scraping data and testing web apps, supporting script-based actions like navigating to URLs, filling forms, and taking screenshots within continuous workflows.

What are the limitations of automating web apps with a persistent browser context?▼

While stateful web automation reduces session recreation, it enforces safe operations and error handling, and requires choosing between standalone server or Chrome extension mode depending on your environment.

Related Skills

Explore More Software Engineering Skills→
blueskies1818blueskies1818
1

browser-control

Automate browser actions and launch system applications via Playwright.

Community
Intermediate
Sonder4Sonder4
27

bfd-fault-logger

Record and classify STM32 hardware faults into structured reports.

Community
Advanced
CleanExpoCleanExpo
1

playwright-browser

Automate headless browser tasks and end-to-end tests with Playwright.

Community
Advanced
SecurityRoninSecurityRonin
1

browser-automation

Automate browser tasks and testing across Playwright, Puppeteer, Selenium, and CDP workflows.

Official
Intermediate