dev-browser

Automate browser tasks with persistent page state using Node.js and Playwright.

16|5|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/Xaiver03/openwork-cn --skill dev-browser-xaiver03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-browser
Source: https://github.com/Xaiver03/openwork-cn/tree/main/apps/desktop/skills/dev-browser
Command: npx skills add https://github.com/Xaiver03/openwork-cn --skill dev-browser-xaiver03

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automating repetitive browser workflows is tedious and error-prone; this Skill maintains a persistent page state across automation steps to ensure context is preserved and tasks run smoothly.

Core Features & Use Cases

  • Persistent sessions: Keep pages open across script executions to handle multi-step tasks without reloading context.
  • Website automation: Navigate, fill forms, take screenshots, extract data, and run tests in a cohesive workflow.
  • Use Case: Imagine repeatedly testing a checkout flow across multiple pages; this Skill automates navigation, form completion, and verification in a single run.

Quick Start

Start the dev-browser server, then create named pages and begin scripting small, focused actions that build into larger automation.

Frequently Asked Questions about dev-browser

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

FAQPage Schema
How do I automate web workflows while keeping page state persistent across executions?

Browser automation with persistent sessions maintains page state across script executions, allowing multi-step tasks like navigating sites and filling forms to run without reloading context. The dev-browser stack uses Node.js and Playwright to orchestrate these repeatable workflows.

Can I take screenshots and scrape data from web apps using Playwright in a single run?

Yes, Playwright web automation supports taking screenshots and scraping data within a single cohesive workflow. Scripts orchestrate website navigation, form completion, and data extraction across multiple pages to automate repetitive tasks.

Does browser automation support testing checkout flows across multiple pages?

Browser automation supports testing checkout flows across multiple pages by maintaining persistent sessions. It automates navigation, form filling, and verification sequentially to handle multi-step tasks without losing context between pages.

Do I need Node.js to run web automation scripts with persistent page state?

Yes, Node.js is required to run web automation scripts with persistent page state. The local dev-browser stack relies on a Node.js environment to execute Playwright scripts that orchestrate browser tasks and maintain sessions.

What is the best way to handle multi-step web automation tasks without reloading context?

The best way to handle multi-step web automation tasks is using persistent sessions that keep pages open across script executions. This approach preserves page state and ensures context is maintained without reloading between actions.