browse
A fast headless-browser capability for QA and dogfooding: navigate, interact, read state, and screenshot the running application from within a session.
Anatomy
| Parent repo | garrytan/gstack |
|---|---|
| Path | skills/browse |
| Trigger conditions | Slash command: /browse (also invoked by qa and design-review skills) |
| Instruction format | yaml-frontmatter-md |
| Required tools | headless-browser |
| Reusability | stack-specific |
| Complexity | high |
| Ships scripts / examples / tests / boundaries | yes / yes / no / yes |
Failure modes
Browser environment drift (profiles, cookies, viewport quirks) is the recurring operational tax of any browser-dependent skill.
Verdict
Infrastructure more than procedure: the tool-layer capability that gstack's verification loops are built on. Evidence-based UI verification starts here.
Related skills
Blocks the agent from claiming work is complete, fixed, or passing until it has run verification commands and confirmed output. Evidence…
Forces root-cause investigation before any fix: reproduce, hypothesize one cause at a time, test the hypothesis, then patch. Bans…
Frequently asked questions
What does the browse skill do?
A fast headless-browser capability for QA and dogfooding: navigate, interact, read state, and screenshot the running application from within a session.
When does browse trigger?
Its stated trigger: Slash command: /browse (also invoked by qa and design-review skills). Trigger precision is a scored reliability dimension.