dev-browser

Automate browser interactions with persistent page state across script executions.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/davzucky/iceberg-explorer --skill dev-browser-davzucky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-browser
Source: https://github.com/davzucky/iceberg-explorer/tree/main/.opencode/skill/dev-browser
Command: npx skills add https://github.com/davzucky/iceberg-explorer --skill dev-browser-davzucky

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Browser automation with a persistent page state enables you to perform repeatable website interactions across script executions, reducing setup time and manual steps for frequent tasks.

Core Features & Use Cases

  • Persisted browser sessions: maintain login state, cookies, and localStorage across runs to streamline multi-step workflows.
  • Incremental scripting: write small, focused scripts that perform one action at a time, then compose them for larger workflows.
  • Standalone mode by default: run in a dedicated Chromium profile to keep environments isolated and reproducible.
  • Use cases include navigating sites, filling forms, taking screenshots, scraping data, testing web apps, and automating repetitive browser tasks.

Quick Start

Start a standalone browser server and execute a small, single-action script to begin automating your workflow.

Frequently Asked Questions about dev-browser

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

FAQPage Schema
How do I maintain login state and cookies across multiple browser automation script executions?

Persistent browser automation maintains login state, cookies, and localStorage across script runs to enable repeatable website interactions. This reduces setup time for multi-step workflows by keeping the session active between executions.

Can I use Playwright to automate web testing with a dedicated isolated browser profile?

Yes, Playwright browser automation runs in Standalone Mode by default, utilizing a dedicated Chromium profile. This keeps your testing environments isolated and ensures your automated web tasks remain reproducible.

What is the best way to build incremental web scraping scripts for multi-step workflows?

Incremental web scraping involves writing small, focused scripts that perform one action at a time. You can then compose these individual scraping actions together to build larger, more complex browser automation workflows.

Does this browser automation approach require restarting sessions for repetitive tasks like form filling?

No, persistent page state automation eliminates the need to restart sessions for repetitive tasks. It retains your browser state across restarts, allowing you to seamlessly continue form filling, navigating pages, and taking screenshots.

What limitations exist when using persistent page state for web app testing?

Limitations of persistent state web app testing include potential state pollution between scripts if cookies and localStorage are not managed. Standalone Mode helps mitigate this by isolating the Chromium profile to keep environments reproducible.

Do I need to install Express to run standalone browser automation scripts?

Yes, Express is required as a dependency alongside Playwright to start the standalone browser server. This server manages the persistent page state required for executing your deterministic automation scripts.