UI Visual Debugging
NangoHQ/nango
A skill your agent uses when modifying or visually debugging Nango frontend UI, including packages/webapp, packages/connect-ui, browser interactions, screenshots, and visual regressions.
You must use this skill when debugging web UI bugs or testing interactive components that require multi-step browser interactions.
Install Browser Bug Testing Workflow
$ npx skills add sandgardenhq/sgai --skill browser-bug-testing-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sandgardenhq/sgai browser-bug-testing-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sandgardenhq/sgai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow .claude/skills/browser-bug-testing-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "browser-bug-testing-workflow" agent skill from https://github.com/sandgardenhq/sgai/tree/main/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow into .claude/skills/browser-bug-testing-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-bug-testing-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sandgardenhq/sgai/tree/main/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sandgardenhq/sgai --skill browser-bug-testing-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sandgardenhq/sgai browser-bug-testing-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sandgardenhq/sgai.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow .agents/skills/browser-bug-testing-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "browser-bug-testing-workflow" agent skill from https://github.com/sandgardenhq/sgai/tree/main/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow into .agents/skills/browser-bug-testing-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-bug-testing-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sandgardenhq/sgai --skill browser-bug-testing-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sandgardenhq/sgai browser-bug-testing-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sandgardenhq/sgai.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow .cursor/skills/browser-bug-testing-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "browser-bug-testing-workflow" agent skill from https://github.com/sandgardenhq/sgai/tree/main/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow into .cursor/skills/browser-bug-testing-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-bug-testing-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sandgardenhq/sgai.git --path cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sandgardenhq/sgai --skill browser-bug-testing-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sandgardenhq/sgai browser-bug-testing-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sandgardenhq/sgai.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow .gemini/skills/browser-bug-testing-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "browser-bug-testing-workflow" agent skill from https://github.com/sandgardenhq/sgai/tree/main/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow into .gemini/skills/browser-bug-testing-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-bug-testing-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sandgardenhq/sgai browser-bug-testing-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sandgardenhq/sgai --skill browser-bug-testing-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sandgardenhq/sgai.git skills-src && mkdir -p .github/skills && cp -r skills-src/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow .github/skills/browser-bug-testing-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "browser-bug-testing-workflow" agent skill from https://github.com/sandgardenhq/sgai/tree/main/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow into .github/skills/browser-bug-testing-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-bug-testing-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sandgardenhq/sgai --skill browser-bug-testing-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sandgardenhq/sgai browser-bug-testing-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sandgardenhq/sgai.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow .opencode/skills/browser-bug-testing-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "browser-bug-testing-workflow" agent skill from https://github.com/sandgardenhq/sgai/tree/main/cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow into .opencode/skills/browser-bug-testing-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-bug-testing-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
browser-bug-testing-workflow- GitHub stars
- 137
- Token cost
- ~3.7k tokens
- SKILL.md length
- 789 words
- Files
- 1
- Skills in repo
- 53
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
You must use this skill when debugging web UI bugs or testing interactive components that require multi-step browser interactions.
- Works in 5 steps: Server Setup with Tmux → Browser Navigation → UI Interaction Patterns → …
- Debugging web UI bugs
- SKILL.md covers Overview, When to Use, Core Workflow Pattern and Quick Reference, plus 10 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Browser Bug Testing Workflow is an agent skill from sandgardenhq/sgai. You must use this skill when debugging web UI bugs or testing interactive components that require multi-step browser interactions. Automates common UI testing patterns for debugging web applications - starting servers, navigating to pages, interacting with form elements, and verifying expected behaviors without manual step-by-step Playwright commands
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Browser testing, Test strategy and Frontend development. It works with Playwright and tmux. The repository describes itself as: Sandgarden AI Software Factory.
When your agent uses it
- Debugging web UI bugs
- Testing interactive components that require multi-step browser interactions
Example prompts
- “/browser-bug-testing-workflow”
Requirements
- Python 3
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Server Setup with Tmux
- Browser Navigation
- UI Interaction Patterns
- Verification and Validation
- Cleanup and Results
What it can do on your machine
Read from SKILL.md and the folder at commit 9efbb7b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript, bash and css).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Browser Bug Testing Workflow loads about 3.7k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 789 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 789 words (~3,695 tokens).
“This skill provides a structured workflow for automated browser testing during UI bug investigation. It combines tmux session management for server processes with Playwright browser automation to create reproducible testing scenarios without manual intervention.”
- name
- browser-bug-testing-workflow
- metadata.requires
- run-long-running-processes-in-tmux
Files
Just SKILL.md in cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow of sandgardenhq/sgai.
Open the folder on GitHubat commit 9efbb7b
Compare with similar skills
Browser Bug Testing Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Browser Bug Testing Workflow this skillsandgardenhq/sgai | 137 | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| UI Visual DebuggingNangoHQ/nango | 13k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Playwrightmagnus919/agent-skills | 113 | — | ~3.4k | Automated safety check: Notes | MIT | |
| Activitypub TestingMicrock/ordinary-claude-skills | 403 | — | ~712 | Automated safety check: Pass | Custom licence | |
| Testingkortix-ai/suna | 20k | — | ~3.6k | Automated safety check: Notes | Custom licence | |
| Shogun Screenshotyohey-w/multi-agent-shogun | 1.4k | — | ~901 | Automated safety check: Notes | MIT |
Similar skills
Playwright
magnus919/agent-skills
Operate Playwright for browser automation end to end: author and debug E2E test suites (robust locators, network interception and mocking, parallel workers, accessibility snapshot checks), wire them…
Activitypub Testing
Microck/ordinary-claude-skills
Testing patterns for PHPUnit and Playwright E2E tests. An agent skill from Microck/ordinary-claude-skills.
Testing
kortix-ai/suna
A skill your agent uses for every Kortix test task, behavior change, bug fix, refactor, API route change, CLI change, SDK change, browser journey, test failure, coverage question, local benchmark…
Shogun Screenshot
yohey-w/multi-agent-shogun
スクリーンショットの取得・加工を行う。ローカルスクショから最新画像を取得、 PlaywrightでWebページをキャプチャ、画像のトリミング・リサイズ、機微情報を黒塗りマスキング。
Playwright Debug
voicetreelab/voicetree
This skill should be used when the user asks to "debug the electron app", "connect playwright to VoiceTree", "take screenshots of the running app", "interact with the live UI", "inspect the running…
More from sandgardenhq/sgai
All 53 skills in this repoRoot Cause Tracing
sandgardenhq/sgai
A skill your agent uses when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation…
Condition Based Waiting
sandgardenhq/sgai
A skill your agent uses when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state…
Defense In Depth
sandgardenhq/sgai
A skill your agent uses when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally…
Agent Native Architecture
sandgardenhq/sgai
Build AI agents using prompt-native architecture where features are defined in prompts, not code.
Adhoc
sandgardenhq/sgai
Run and manage ad-hoc AI prompts in sgai workspaces without starting a full agentic session.
Create Opencode Agents
sandgardenhq/sgai
Guide for creating custom opencode agents with proper configuration, permissions, path-based delegation, work splitting, and strict status envelopes.
Related
Works with
Categories
Questions about Browser Bug Testing Workflow
What does Browser Bug Testing Workflow do?
You must use this skill when debugging web UI bugs or testing interactive components that require multi-step browser interactions. Browser Bug Testing Workflow is an agent skill from sandgardenhq/sgai. You must use this skill when debugging web UI bugs or testing interactive components that require multi-step browser interactions.
When should I use Browser Bug Testing Workflow?
Browser Bug Testing Workflow fits situations like: debugging web UI bugs; testing interactive components that require multi-step browser interactions.
How do I install Browser Bug Testing Workflow in Claude Code?
Run `npx skills add sandgardenhq/sgai --skill browser-bug-testing-workflow -a claude-code`. Or copy the skill folder (cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow in sandgardenhq/sgai) into .claude/skills/browser-bug-testing-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Browser Bug Testing Workflow in Codex?
Run `npx skills add sandgardenhq/sgai --skill browser-bug-testing-workflow -a codex`. Or copy the skill folder (cmd/sgai/skel/.sgai/skills/browser-bug-testing-workflow in sandgardenhq/sgai) into .agents/skills/browser-bug-testing-workflow in your project. Codex loads it when a task matches its description.
Can I use Browser Bug Testing Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sandgardenhq/sgai --skill browser-bug-testing-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser-bug-testing-workflow, .gemini/skills/browser-bug-testing-workflow, .github/skills/browser-bug-testing-workflow and .opencode/skills/browser-bug-testing-workflow in your project.
What does Browser Bug Testing Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Browser Bug Testing Workflow is instructions for the agent only. Our summary lists: Python 3.
Does Browser Bug Testing Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Browser Bug Testing Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Browser Bug Testing Workflow use?
Browser Bug Testing Workflow has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Browser Bug Testing Workflow use?
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Browser Bug Testing Workflow?
Skills that share tags, products or a category with Browser Bug Testing Workflow: UI Visual Debugging (NangoHQ/nango, 13k stars), Playwright (magnus919/agent-skills, 113 stars), Activitypub Testing (Microck/ordinary-claude-skills, 403 stars) and Testing (kortix-ai/suna, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Browser Bug Testing Workflow?
sandgardenhq (a GitHub organization) maintains it in sandgardenhq/sgai, which has 137 GitHub stars. The repository holds 53 skills in this directory. The repository was last updated on September 21, 2026.
Source: sandgardenhq/sgai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.