dev-browser

Automate browser tasks with persistent page state across script executions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Browser automation with persistent page state to simplify multi-step web tasks across script executions and sessions.

Core Features & Use Cases

  • Standalone mode vs extension mode for flexibility across projects
  • Persist pages across scripts, capture screenshots, and inspect accessibility with ARIA snapshots
  • Programmatic browser control for testing, data extraction, and site automation across websites

Quick Start

Start by launching the standalone server and begin writing small, focused scripts to automate browser tasks.

Frequently Asked Questions about dev-browser

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

FAQPage Schema
How do I maintain browser state across multiple web automation script executions?

To maintain browser state across script executions, this Skill preserves page state automatically between sessions. It enables you to pause and resume multi-step web tasks without losing your current page context or session data.

Can I use Playwright to automate form filling and scrape data with persistent sessions?

Yes, you can automate form filling and scrape data using persistent browser sessions. It supports navigating websites, filling forms, taking screenshots, and extracting data while keeping the page state intact across executions.

What do I need to set up browser automation with state persistence locally?

Browser automation with state persistence requires a local OpenCode setup and Skill scripts located under skills/dev-browser. You also need the client API to access page management and ARIA snapshot features for accessibility inspection.

Does browser automation support both standalone scripts and extension modes?

Browser automation supports both standalone and extension modes for flexibility across projects. Standalone mode launches an independent server, while extension mode integrates browser control into your existing automation workflows.

How do I capture screenshots and inspect accessibility during web testing?

You capture screenshots and inspect accessibility by utilizing built-in ARIA snapshot features. This allows you to test web apps programmatically and verify page structures directly through the client API during automation tasks.