skills.rest
1thirteeng3
1thirteeng3COMMUNITY
Explore all skills by this author →
GitHub

dev-browser

Automate browser interactions while preserving page state across script runs.

Updated Mar 24, 2026
Search Tags:#automation#screenshots#extension#playwright#browser#web-automation#state-persistence
One-click install
npx skills add https://github.com/1thirteeng3/greenmoire --skill dev-browser-1thirteeng3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-browser
Source: https://github.com/1thirteeng3/greenmoire/tree/main/integrations/oh-my-openagent/src/features/builtin-skills/dev-browser
Command: npx skills add https://github.com/1thirteeng3/greenmoire --skill dev-browser-1thirteeng3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates browser interactions while preserving page state across script executions, enabling repeatable automation across tasks that span multiple sessions.

Core Features & Use Cases

  • Stateful browser sessions: keep pages open and connected across script runs.
  • Two modes: Standalone mode launches a fresh Chromium instance; Extension mode connects to an existing Chrome session.
  • Scripted interactions: navigate, click, fill forms, take screenshots, and extract data.
  • Visual feedback and ARIA snapshot support to inspect page state.

Quick Start

Navigate to a URL, perform a sequence of interactions on the page, and capture results in a scripted workflow.

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

Persistent browser automation preserves page state across separate script executions, keeping pages open and connected. This enables repeatable web automation tasks spanning multiple sessions without losing page context.

Can I connect Playwright automation to an existing Chrome browser session?▼

Yes, extension mode connects web automation scripts directly to an existing Chrome session. Alternatively, standalone mode launches a fresh Chromium instance for isolated browser automation tasks.

What's the best way to automate filling forms and taking screenshots in a web app?▼

Scripted browser automation supports navigating URLs, clicking elements, filling forms, and taking screenshots. It provides visual feedback and ARIA snapshot support to inspect page state during web app testing.

Does browser automation work for scraping data across multiple sessions?▼

Stateful browser sessions enable scraping data across multiple script runs by preserving page state. This ensures repeatable data extraction from web apps where maintaining login state or page context is required.

When should I use standalone mode versus extension mode for web automation?▼

Use standalone mode to launch a fresh Chromium instance for isolated browser automation. Use extension mode to connect to an existing Chrome session when preserving an active browsing environment.

Related Skills

Explore More Software Engineering Skills→
X-School-AcademyX-School-Academy
19

init-playwright

Initialize and verify Playwright CLI, Google Chrome, and the Playwright MCP Bridge extension.

Official
Intermediate
mupengi-botmupengi-bot
11

data-scraper

Fetch HTML from URLs and extract structured data into JSON or Markdown.

Community
Intermediate
sfc-gh-dflipposfc-gh-dflippo
34

Playwright MCP

Automate browser testing and UI validation for web applications using MCP tools.

Community
Intermediate
SecurityRoninSecurityRonin
1

browser-automation

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

Official
Intermediate