dev-browser

Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is dev-browser in SawyerHood/dev-browser

Dev Browser

A CLI for controlling browsers with sandboxed JavaScript scripts.

Installation

npm install -g dev-browser
dev-browser install

Usage

Run dev-browser --help to learn more.

Named daemon-launched browsers persist by default. For unattended work, --idle-timeout 5m closes each launched browser after inactivity while preserving its profile and login state. The setting never closes Chrome attached with --connect; use --idle-timeout 0 to disable configured cleanup.

Repository: numman-ali/n-skills
Path: skills/automation/dev-browser/skills/dev-browser/SKILL.md
Commit: b1c6173

Last updated: 8 days ago
First committed: 7 months ago

Canonical home

SawyerHood/dev-browser

In sync

since Jul 24, 2026

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.