dev-browser

Automate browser tasks with persistent page state across script executions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Fuzen2478/only-my-opencode --skill dev-browser-fuzen2478
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-browser
Source: https://github.com/Fuzen2478/only-my-opencode/tree/main/src/features/builtin-skills/dev-browser
Command: npx skills add https://github.com/Fuzen2478/only-my-opencode --skill dev-browser-fuzen2478

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Dev Browser Skill solves the challenge of repetitive browser automation tasks by maintaining page state across script executions, enabling multi-step workflows without reinitializing the browser.

Core Features & Use Cases

  • Stateful sessions: preserve page state across runs for smooth multi-action workflows.
  • Dual modes: Standalone mode and Extension mode to match local or authenticated workflows.
  • Guided scripting: write small, focused scripts that perform single actions (navigate, click, fill, screenshot) and progress through a workflow.
  • Use Case: Imagine automating a login and data extraction flow across several pages, saving time and reducing errors.

Quick Start

Start by setting up the skill in either standalone or extension mode and then create a minimal script in skills/dev-browser to perform a simple action like opening a page and taking a screenshot.

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 testing while keeping page state across multiple script executions?

Stateful browser automation preserves page state across runs, enabling multi-step web testing workflows without reinitializing the browser. You write focused scripts that navigate, click, and fill forms sequentially across sessions.

What's the best way to automate a multi-step login and data extraction flow without losing session state?

Automating a login and data extraction flow is best handled with persistent page state, allowing sequential scripts to maintain authentication and DOM state across multiple pages without restarting the browser session.

Do I need Node.js and npm dependencies to run browser automation scripts?

Yes, you need Node.js and npm dependencies to run these browser automation scripts. The environment requires installing packages locally within the skills directory before executing navigation, clicking, or scraping actions.

Can I run Playwright-style web automation in both standalone and extension modes?

Yes, web automation supports both standalone and extension modes. Standalone mode runs local workflows directly, while extension mode integrates into authenticated workflows, offering flexibility for different testing and scraping contexts.

How do I write scripts to navigate URLs, fill forms, and take screenshots in a stateful browser environment?

You write small, focused scripts that perform single actions like navigating URLs, clicking elements, filling forms, and taking screenshots. Each script progresses through a guided workflow using the preserved page state.

Why does my browser automation require reinitializing the browser between page actions?

Browser automation requires reinitialization when page state is not preserved between executions. Using a stateful session approach eliminates this by keeping the browser context active, allowing multi-action workflows to run continuously.