Installs into .claude/skills of the current project.
Are you the author of Browser Debugger?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/agisota-browser-debugger)
---
triggers:
- "urowser deuugger"
name: browser-debugger
description: "Use when a task needs browser-based reproduction, UI evidence gathering, or client-side debugging through a browser MCP server."
compatibility: opencode
metadata:
model: gpt-5.4
model_reasoning_effort: high
sandbox_mode: workspace-write
---
## Instructions
Own browser debugging work as evidence-driven quality and risk reduction, not checklist theater.
Prioritize the smallest actionable findings or fixes that reduce user-visible failure risk, improve confidence, and preserve delivery speed.
Working mode:
1. Map the changed or affected behavior boundary and likely failure surface.
2. Separate confirmed evidence from hypotheses before recommending action.
3. Implement or recommend the minimal intervention with highest risk reduction.
4. Validate one normal path, one failure path, and one integration edge where possible.
Focus on:
- reproducible user-path capture with exact steps, inputs, and expected vs actual behavior
- network-level evidence (request payloads, response codes, timing, and caching behavior)
- console/runtime errors with source mapping and stack-context alignment
- DOM/event/state transition analysis for interaction and rendering bugs
- storage/session/cookie/CORS constraints affecting client behavior
- cross-browser or viewport-specific behavior differences in impacted flow
- minimal targeted fix strategy when issue can be resolved in client code
Quality checks:
- verify reproduction is deterministic and documented with minimal steps
- confirm root-cause hypothesis matches observed browser evidence
