UI Test
AI-powered adversarial UI testing via the browse CLI. Analyzes git diffs to test only what changed, or explores the full app to find bugs. Tests functional correctness, accessibility, responsive layout, and UX heuristics. Use when the user asks to test UI changes, QA a pull request, audit accessibility, or run exploratory testing. Supports local browser (localhost) and remote Browserbase (deployed sites).
Install
/plugin marketplace add browserbase/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add browserbase/skills --skill ui-testgit clone --depth 1 https://github.com/browserbase/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/ui-test ~/.claude/skills/ui-testPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# UI Test — Agentic UI Testing Skill Test UI changes in a real browser. Your job is to **try to break things**, not confirm they work. Three workflows: - **Diff-driven** — analyze a git diff, test only what changed - **Exploratory** — navigate the app, find bugs the developer didn't think about - **Parallel** — fan out independent test groups across multiple Browserbase browsers ## How Testing Works The main agent **coordinates** — it plans test strategy, delegates to sub-agents, and merges results. Sub-agents do the actual browser testing. ### Planning: multiple angles, then execute once **You MUST complete all three planning rounds yourself and output them before launching any sub-agents.** Planning happens in your own response — it is NOT delegated to sub-agents. Do not skip ahead to execution. **Round 1 — Functional:** What are the core user flows? What should work? Write out each test as: action → expected result. **Round 2 — Adversarial:** Re-read Round 1. What did you miss? Think about: different user types/roles, error paths, empty states, race conditions, edge inputs (empty, huge, special chars, rapid clicks). **Round 3 — Coverage gaps:** Re-read Rounds 1–2. What about: accessibility (axe-core, keyboard-only), mobile viewports, console errors, visual consistency with the rest of the app? **Deduplicate:** Merge all three rounds into one numbered list of tests. Remove overlaps. Assign each test to a group (e.g. Group A, Group B).
Details
- Skill name
ui-test- Repository
- browserbase/skills
- Path
skills/ui-test/SKILL.md- Repo updated
- 17 November 2026
- Copies
- Found in 2 GitHub repos
FAQ
What does the UI Test skill do?
AI-powered adversarial UI testing via the browse CLI. Analyzes git diffs to test only what changed, or explores the full app to find bugs. Tests functional correctness, accessibility, responsive layout, and UX heuristics. Use when the user asks to test UI changes, QA a pull request, audit accessibility, or run exploratory testing. Supports local browser (localhost) and remote Browserbase (deployed sites).
How do I install the UI Test skill?
Claude Code plugin: /plugin marketplace add browserbase/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is UI Test popular?
It lives in browserbase/skills, which has 3,757 GitHub stars and 239 forks.
Related skills
Autobrowse
3.8kbrowserbase/skills
Self-improving browser automation via the auto-research loop. Iteratively runs a browsing task, reads the trace, and improves the navigation skill (strategy.md) until it reliably passes. Supports parallel runs across multiple tasks using sub-agents. Use when you want to build or improve browser automation skills for specific website tasks.
Browser
3.8kbrowserbase/skills
Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from websites, take screenshots, fill forms, click buttons, or interact with web applications. Supports remote Browserbase sessions with Browserbase Identity, Verified browsers, automatic CAPTCHA solving, and residential proxies — ideal for protected websites and JavaScript-heavy pages.
Browser to API
3.8kbrowserbase/skills
Turn a website's observable HTTP traffic into a best-effort OpenAPI 3.1 spec by analyzing a `browser-trace` capture. Use when the user wants to discover/extract API endpoints from a browser session, build an OpenAPI doc from network traffic, or document a third-party site's XHR/fetch surface for client integration.
Test Driven Development
3.3krpamis/comet
TDD guidance for feature implementation. Follow test-driven development practices with red-green-refactor workflow.
Browser Harness
4.3kdavidondrej/skills
Direct browser control via CDP. Use when the user wants to automate, scrape, test, or interact with web pages. Connects to the user's already-running Chrome.
Playwright Skill
7.2ktech-leads-club/agent-skills
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing. Do NOT use for quick page debugging or network inspection (use chrome-devtools instead).
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.