skills.rest
AIKAGRYA
AIKAGRYAOFFICIAL
Explore all skills by this author →
GitHub

dharma-browse

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

1|3|Updated Mar 9, 2026
Search Tags:#browser automation#navigation#screenshot capture#web inspection#state verification#qa handoff
One-click install
npx skills add https://github.com/AIKAGRYA/dharma_swarm --skill dharma-browse-aikagrya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dharma-browse
Source: https://github.com/AIKAGRYA/dharma_swarm/tree/main/mode_pack/claude/browse
Command: npx skills add https://github.com/AIKAGRYA/dharma_swarm --skill dharma-browse-aikagrya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual browser checks are slow and leave no evidence. This Skill provides a structured mode for navigating web pages, verifying page state, and capturing screenshots so browser-based verification produces consistent, reviewable results. ## Core Features & Use Cases - Fast Navigation: Directs the agent to move through pages quickly using the repo's existing browser workflow or the gstack browse command when available. - State Capture: Requires a navigation result and a state snapshot as output, preserving evidence with screenshots when the result matters. - Tool Discipline: Prevents overuse of browser automation by requiring file or API inspection when those are sufficient. - Use Case: After deploying a dashboard change, use this mode to load the page, verify the rendered state, and capture a screenshot before handing off to QA or incident review. ## Quick Start Use the dharma-browse mode to open the dashboard page, verify it loads correctly, and capture a screenshot of the result.

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 navigate pages with the repo's existing browser workflow or the gstack browse command. It produces a navigation result and a state snapshot, preserving screenshots as evidence 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 mode explicitly directs you to prefer file inspection or API inspection when those are sufficient to answer the question.

What output does a browser verification session produce?▼

Each session must produce two artifacts: a navigation result describing where the browser went, and a state snapshot capturing the page condition. Screenshots are preserved when the result matters for later review.

Can I use this mode without the gstack browse command installed?▼

Yes. The mode prefers the repo's existing browser workflow and only falls back to gstack browse if it is installed and working. It does not require inventing a new browser stack.

What happens after browser verification is complete?▼

The mode typically hands off to dharma-qa for quality review or to dharma-incident-commander when the captured state relates to an incident. The snapshots and screenshots serve as the handoff evidence.

Related Skills

Explore More Software Engineering Skills→
ScotterMonkScotterMonk
37

login-using-querystring

Log in to web applications via URL query string parameters.

Community
Basic
AmitabhainArunachalaAmitabhainArunachala

dharma-browse

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

Community
Basic
metabenchmetabench

browser-verification

Launch demo servers and verify UI rendering in live browsers.

Community
Intermediate
jd-opensourcejd-opensource
299

pentest-race-conditions

Identify and reproduce race conditions and TOCTOU vulnerabilities in web applications.

Official
Advanced