skills.rest
AmitabhainArunachala
AmitabhainArunachalaCOMMUNITY
Explore all skills by this author →
GitHub

dharma-browse

Automates browser navigation, state verification, and screenshot capture for web inspection workflows.

Updated Aug 5, 2026
Search Tags:#browser automation#navigation#web verification#screenshot capture#gstack#state snapshot#qa handoff
One-click install
npx skills add https://github.com/AmitabhainArunachala/dharma_swarmv.01 --skill dharma-browse-amitabhainarunachala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dharma-browse
Source: https://github.com/AmitabhainArunachala/dharma_swarmv.01/tree/main/mode_pack/claude/browse
Command: npx skills add https://github.com/AmitabhainArunachala/dharma_swarmv.01 --skill dharma-browse-amitabhainarunachala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual browser checks during development and incident response are slow and leave no evidence. This Skill provides a repeatable browser-operation mode that navigates pages, captures state snapshots, and preserves screenshots as verifiable artifacts. ## Core Features & Use Cases - Fast Navigation: Drives the existing browser stack or gstack browse to reach target pages quickly without building new automation. - State Capture: Records navigation results and state snapshots so outcomes can be reviewed or handed off. - Evidence Preservation: Saves screenshots or snapshots whenever the result matters for QA or incident review. - Use Case: During a dashboard regression check, use this mode to open the affected page, verify the rendered state, and capture a screenshot before handing off to the QA or incident-commander workflow. ## Quick Start Use the dharma-browse mode to open the dashboard page, verify its rendered state, and capture a screenshot as evidence.

Frequently Asked Questions about dharma-browse

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

FAQPage Schema
How do I automate browser navigation and screenshot capture?▼

Use this mode to drive the repository's existing browser workflow or gstack browse to navigate pages and capture state snapshots. It returns a navigation result and a state snapshot, with screenshots preserved when the outcome matters.

When should I use browser automation instead of API inspection?▼

Use browser automation only when rendered page state or visual verification is required. The Skill explicitly directs you to prefer file inspection or API inspection when those are sufficient to answer the question.

Can I use gstack browse with this browser workflow?▼

Yes, gstack browse is the preferred tool if it is installed and working. Otherwise the mode falls back to the repository's existing browser workflow rather than inventing a new one.

What happens to the screenshots and snapshots after capture?▼

Captured evidence is preserved as part of the required output and typically handed off to the dharma-qa or dharma-incident-commander modes for downstream review, regression analysis, or incident documentation.

What are the limitations of this browser-operation mode?▼

It is a navigation and capture mode only, not a full testing framework. It depends on an existing browser stack being available and defers deeper validation and incident handling to the QA and incident-commander handoff targets.

Related Skills

Explore More Software Engineering Skills→
BenjamindaosonBenjamindaoson

dogfood

Automate exploratory QA testing of web applications and generate structured bug reports.

Community
Advanced
darkroomengineeringdarkroomengineering
41

debug

Automate browser debugging with agent-browser CLI for navigation, screenshots, and snapshots.

Official
Intermediate
NagyViktNagyVikt
2

agent-browser-verify

Automate visual and functional verification of web development servers via browser state and console output.

Community
Advanced
tom-xstom-xs

playwright-cli

Operate a live browser via command line with Playwright.

Community
Advanced