DevBrowser

Automate browser-based UI testing with headless Chromium commands.

2|Updated Jul 26, 2025
One-click install
npx skills add https://github.com/fullykubed/nixos-config --skill devbrowser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: DevBrowser
Source: https://github.com/fullykubed/nixos-config/tree/main/modules/common/claude/skills/DevBrowser
Command: npx skills add https://github.com/fullykubed/nixos-config --skill devbrowser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright.

What problem does it solve?

Manual browser testing, UI verification, and data gathering from web pages are repetitive and error-prone tasks that slow down development.

Core Features & Use Cases

  • Headless browser automation with persistent sessions for repeatable tests
  • Navigate, click, type, wait, and snapshot commands for interactive pages
  • AI-friendly DOM snapshots for reliable automation results

Quick Start

Launch a session, navigate to a target page, and capture a snapshot to verify the UI state.

Frequently Asked Questions about DevBrowser

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

FAQPage Schema
How do I automate web testing with a headless browser?

Automate web testing by using a headless Chromium browser to navigate pages, interact with elements, and capture screenshots. This approach executes commands like click, type, and wait to verify dynamic UI states during development without manual intervention.

Does Playwright support taking AI-friendly DOM snapshots for UI verification?

Playwright supports UI verification by generating AI-friendly DOM snapshots. You can capture these snapshots during a browser automation session to provide structured, reliable representations of the page state for automated analysis.

Can I maintain persistent browser sessions for repeatable CLI testing?

You can maintain persistent browser sessions for repeatable CLI testing. The automation framework implements session-based persistence, allowing sequential commands to execute within the same browser context to preserve state across multiple interactions.

What is the best way to verify dynamic web content during development?

The best way to verify dynamic web content is using a headless browser automation tool that waits for dynamic elements to load. You can execute wait commands before taking screenshots or snapshots to ensure the UI has fully rendered.

How do I navigate and interact with web pages using command line automation?

You navigate and interact with web pages using a CLI that sends commands to a headless Chromium instance. The CLI supports actions like navigate, click, and type, returning structured results directly to your terminal for development testing.

Do I need Playwright installed to run headless browser automation tasks?

You need Playwright installed to run headless browser automation tasks. The framework relies on Playwright as its core dependency to control the headless Chromium browser, execute commands, and return structured automation results.