skills.rest
aniwei
aniweiCOMMUNITY
Explore all skills by this author →
GitHub

dev-browser

Automate browser interactions with persistent page state across script executions.

Updated Feb 3, 2026
Search Tags:#automation#screenshots#Playwright#extension#browser#automate
One-click install
npx skills add https://github.com/aniwei/vitamin-code --skill dev-browser-aniwei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-browser
Source: https://github.com/aniwei/vitamin-code/tree/main/refs/oh-my-opencode/src/features/builtin-skills/dev-browser
Command: npx skills add https://github.com/aniwei/vitamin-code --skill dev-browser-aniwei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides browser automation with persistent page state across script executions, enabling you to maintain session context between runs and reduce repetitive setup when performing iterative browser tasks.

Core Features & Use Cases

  • Persistent pages and named sessions to maintain context across tasks
  • Automate common browser actions: navigate, click, fill forms, and take screenshots
  • Supports standalone mode (new browser instance) and extension mode (control an existing Chrome session) for flexible workflows

Quick Start

Start by installing dependencies and launching the server from the skill directory:

  • cd skills/dev-browser && npm install
  • cd skills/dev-browser && ./server.sh & For extension mode:
  • cd skills/dev-browser && npm install
  • cd skills/dev-browser && npm run start-extension & Wait for the Ready message (standalone) or Extension connected message (extension mode) in the console to begin scripting.

Frequently Asked Questions about dev-browser

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

FAQPage Schema
How do I maintain persistent page state across browser automation script executions?▼

Browser automation with persistent page state maintains session context between script runs, reducing repetitive setup. You use named sessions to keep context across tasks when navigating, filling forms, or scraping data.

Can I automate an existing Chrome session instead of launching a new browser instance?▼

Yes, extension mode lets you control an existing Chrome session. You run the extension relay to connect your scripts to your active browser, while standalone mode launches a new browser instance.

How do I set up Playwright browser automation with Node.js and npm?▼

To set up Playwright browser automation, navigate to the skill directory and run npm install. Then start the server and wait for the Ready message in the console to begin scripting your web workflows.

What browser actions can I automate for testing apps and scraping data?▼

You can automate navigating to URLs, clicking elements, filling forms, taking screenshots, scraping data, testing apps, and automating browser workflows using either standalone or extension modes.

Do I need to restart my browser automation server for every script run?▼

No, the server maintains persistent pages and named sessions. This design preserves your session context across multiple script executions, eliminating the need to restart or repeat login setups.

Related Skills

Explore More Software Engineering Skills→
theslashdojotheslashdojo

npm-scripts

Execute npm scripts and npx commands with argument forwarding and environment variables.

Official
Intermediate
SakshamKandelSakshamKandel

scrape

Extract structured data from web pages into JSON-ready results.

Community
Intermediate
Women-Coding-CommunityWomen-Coding-Community
10

playwright-cli

Automate browser interactions for web testing, form filling, screenshots, and data extraction.

Official
Advanced
KanTrunKanTrun

chrome-devtools

Automate browser tasks with Puppeteer CLI scripts and JSON outputs.

Community
Advanced