dev-browser

Automate browser interactions with persistent page state across script executions.

940|90|Updated Jan 12, 2026

Search Tags:#automation #screenshots #Playwright #web-testing #browser #web-scrape #session-persistence

Ready to run

npx skills add https://github.com/iannuttall/ralph --skill dev-browser-iannuttall

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-browser
Source: https://github.com/iannuttall/ralph/tree/main/skills/dev-browser
Command: npx skills add https://github.com/iannuttall/ralph --skill dev-browser-iannuttall

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates browser interactions with persistent page state across script executions, reducing repetitive manual steps when testing, scraping, or interacting with websites.

Core Features & Use Cases

Persistent browser state: Maintain cookies, localStorage, and session data across script runs for seamless multi-step workflows.
Element interaction: Navigate to URLs, click elements, fill forms, and capture screenshots to verify UI behavior.
Use Case: QA can automate the login flow on a web app across environments and routinely verify visual and data-driven outcomes.

Quick Start

Example: open https://example.com, log in with test credentials, and take a screenshot while logging the page title.

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 session persistence across multiple Playwright script executions?▼

Browser session persistence across Playwright script executions maintains cookies, localStorage, and session data automatically. It enables seamless multi-step workflows for QA testing or web scraping without needing to repeat manual login steps.

Can I automate filling forms and clicking elements during web testing?▼

Automating form filling and element clicking is supported for web testing workflows. The Skill interacts with web pages by navigating to URLs, clicking elements, filling forms, and capturing screenshots to verify UI behavior.

What is the best way to take screenshots during web automation to verify UI behavior?▼

Taking screenshots during web automation verifies UI behavior by capturing the page state after interactions. You can navigate to a URL, perform actions like logging in, and take a screenshot to validate visual and data-driven outcomes.

Does browser automation work for scraping data and testing web apps across different environments?▼

Browser automation works for scraping data and testing web apps across environments. The modular client-server approach uses scripts for deterministic tasks, allowing you to routinely verify outcomes in real-world workflows.

Why do I need to repeat login steps every time I run a browser automation script?▼

Repeating login steps in browser automation scripts is eliminated by persistent page state. The Skill retains cookies and session data across script runs, reducing repetitive manual configuration when interacting with websites.

Do I need any external dependencies or a specific environment setup to use dev-browser?▼

No external dependencies are required to use dev-browser. The Skill relies on a modular client-server approach with a dedicated extension and relay setup, declaring any necessary dependencies directly within its package.json file.