dev-browser

Automate browser interactions with persistent page state across scripts.

19|4|Updated Dec 23, 2021
One-click install
npx skills add https://github.com/raas-dev/configent --skill dev-browser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-browser
Source: https://github.com/raas-dev/configent/tree/main/etc/claude-code/skills/dev-browser
Command: npx skills add https://github.com/raas-dev/configent --skill dev-browser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, @hono/node-server, @hono/node-ws, express, hono, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides browser automation with persistent page state across script executions, enabling you to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows without losing context. It reduces repetitive clicking and keeps session data intact across steps.

Core Features & Use Cases

  • Persistent pages: Reuse named pages across scripts to maintain state (cookies, localStorage) for multi-step tasks.
  • Two modes: Standalone browser or Chrome extension integration to fit your workflow.
  • Automation primitives: Navigate, click, fill, screenshot, and ARIA snapshot integration for accessibility/testing.
  • Use Case: Automate login to a site, perform a search, and extract results in a single flow.

Quick Start

Go to https://example.com, log in, and capture a screenshot. After that you can reuse pages across scripts to complete a multi-step workflow without reloading login state.

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 my login session active across multiple steps?

Browser automation with persistent page state maintains cookies and localStorage across script executions, so you stay logged in and preserve session data without re-authenticating. Named pages let you reuse the same browser context for multi-step workflows like login, search, and data extraction in a single flow.

Can I use Playwright for web automation with persistent state instead of restarting the browser each time?

Playwright-based automation with persistent pages reuses named browser contexts across scripts, eliminating repetitive setup and maintaining authenticated sessions. This approach works in standalone mode or as a Chrome extension, adapting to your workflow preferences.

What's the best way to automate form filling and screenshots on websites I need to log into?

Navigate to the site, log in once, then reuse that persistent page context to fill forms, take screenshots, and extract data without losing authentication. The same named page carries your session across all subsequent automation steps.

How do I scrape web data while maintaining an authenticated session across multiple pages?

Persistent browser contexts preserve cookies and login state, letting you navigate multiple pages and extract data without re-authenticating. Script-driven page actions access named pages that retain your session throughout the workflow.

Can I integrate accessibility testing into my browser automation workflow?

ARIA snapshot tooling integrates with browser automation to track accessibility-aware interactions, enabling you to test web app usability and validate page structure alongside functional automation tasks.

Does browser automation work as a standalone tool or do I need to set up a Chrome extension?

Browser automation operates in two modes: standalone for direct script control, or Chrome extension integration for workflows that require extension-level browser access. Choose the mode that fits your automation context.