dev-browser

Automate browser tasks with persistent page state across script executions.

1.0k|105|Updated Jan 2, 2026

Search Tags:#playwright #scripts #web-testing #browser-automation #extension-mode

Ready to run

npx skills add https://github.com/numman-ali/n-skills --skill dev-browser-numman-ali

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides persistent browser automation that maintains page state across script executions and sessions, enabling reliable multi-step workflows without losing context between runs.

Core Features & Use Cases

Persistent page state: Run small, focused scripts that build toward larger automations, reusing browser context across executions.
Standalone and extension modes: Choose to spawn a fresh browser instance or connect to an existing one for authed interactions.
Use cases include site navigation, form filling, taking screenshots, and web data scraping.

Quick Start

From the skill root, install and run:

cd skills/dev-browser && npm i
npm run start-server
npm run start-extension

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 tasks while keeping page state between script runs?▼

Browser automation with persistent page state lets you run small, focused scripts that build on each other without losing context. This Skill uses Playwright-based runtime to maintain your browser session across executions, so navigation, form data, and authentication persist between runs.

Can I use Playwright for web testing and form filling automation?▼

Yes. This Skill automates Playwright-based workflows for web testing, form filling, screenshot capture, and data scraping. It supports both standalone browser instances and connection to existing ones, making it suitable for testing authenticated workflows and multi-step interactions.

What's the difference between standalone and extension modes for browser automation?▼

Standalone mode spawns a fresh browser instance for each session, ideal for isolated tests. Extension mode connects to an existing browser, preserving authentication and user context—useful for workflows that require logged-in interactions or reusing established sessions.

How do I set up persistent browser automation for multi-step workflows?▼

Install dependencies with `npm i`, start the local server with `npm run start-server`, then launch extension mode with `npm run start-extension`. This sets up the Playwright runtime and local server needed to maintain page state across incremental script executions.

Can I build complex automations from smaller browser scripts?▼

Yes. This Skill supports incremental workflow assembly—you write deterministic small scripts that reuse the persistent browser context across executions, letting you compose larger automations step by step while maintaining navigation history and filled form data.

Does browser automation work for scraping data and taking screenshots?▼

Yes. Common use cases include site navigation, web data scraping, and screenshot capture. Persistent page state ensures multi-step scraping workflows can navigate through pages and extract data without re-authenticating or losing your position in the site.