Communitygithub.com

browserbase/ui-test

Tests d'interface utilisateur adverses alimentés par l'IA via la CLI browse. Analyse les différences git pour tester uniquement ce qui a changé, ou explore l'application entière pour trouver des bugs. Teste l'exactitude fonctionnelle, l'accessibilité, la mise en page réactive et les heuristiques UX. À utiliser lorsque l'utilisateur demande de tester des changements d'interface, de faire une QA d'une pull request, d'auditer l'accessibilité ou d'effectuer des tests exploratoires. Prend en charge le navigateur local (localhost) et le Browserbase distant (sites déployés).

Qu'est-ce que ui-test ?

Cette compétence permet d'effectuer des tests d'interface utilisateur adverses, alimentés par l'IA, via la CLI `browse`. Elle est particulièrement utile pour les développeurs et les ingénieurs QA qui souhaitent automatiser la détection de bugs dans les interfaces web, en se concentrant sur les changements récents (via l'analyse des diffs git) ou en explorant l'ensemble de l'application. La compétence évalue plusieurs aspects : l'exactitude fonctionnelle, l'accessibilité, la mise en page réactive et les heuristiques UX. Elle prend en charge à la fois les environnements locaux (localhost) et les sites déployés via Browserbase, ce qui la rend flexible pour divers flux de développement. En résumé, elle agit comme un testeur QA automatisé qui identifie les régressions, les problèmes d'accessibilité et les incohérences d'interface avant même qu'un humain ne les remarque.

Compatible avec~Claude Code~Codex CLI~Cursor
Part ofDesign & UI
npx skills add https://github.com/browserbase/skills/tree/main/skills/ui-test
Voir l'original→Voir toutes les compétences

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Documentation

Que fait ui-test ?

Tests d'interface utilisateur adverses alimentés par l'IA via la CLI browse. Analyse les différences git pour tester uniquement ce qui a changé, ou explore l'application entière pour trouver des bugs. Teste l'exactitude fonctionnelle, l'accessibilité, la mise en page réactive et les heuristiques UX. À utiliser lorsque l'utilisateur demande de tester des changements d'interface, de faire une QA d'une pull request, d'auditer l'accessibilité ou d'effectuer des tests exploratoires. Prend en charge le navigateur local (localhost) et le Browserbase distant (sites déployés).

Individual skills in this repo

This repo contains 10 individual skills — each has its own dedicated page.

browserbase/autobrowse

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.

browserbase/browser

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.

browserbase/browserbase-cli

Use the Browserbase CLI (`browse`) for Browserbase Functions and platform API workflows. Use when the user asks to run `browse`, deploy or invoke functions, manage sessions, projects, contexts, or extensions, fetch a page through the Browserbase Fetch API, search the web through the Browserbase Search API, or scaffold starter templates. Prefer the Browser skill for interactive browsing; use the top-level `browse` driver commands (`browse open`, `browse get`, etc.) only when the user explicitly wants the CLI path.

browserbase/browser-to-api

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.

browserbase/browser-trace

Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page summaries back into an agent loop so its next iteration learns from the last one.

browserbase/cookie-sync

Sync cookies from local Chrome to a Browserbase persistent context so the browse CLI can access authenticated sites. Use when the user wants to browse as themselves, sync cookies, or log into sites via Browserbase.

browserbase/event-prospecting

Event prospecting skill. Takes a conference / event speakers URL, extracts the people, filters their companies against the user's ICP, then deep-researches only the speakers at ICP-fit companies. Outputs a person-first HTML report where each card answers "why should the AE talk to this person?" with all public links and a one-click DM opener. Use when the user wants to: (1) find leads at a specific conference, (2) prep for an event, (3) research event speakers, (4) build a target list from a sponsor/exhibitor page, (5) scrape conference speakers and rank by ICP fit. Triggers: "find leads at {event}", "research speakers at", "prospect this conference", "stripe sessions leads", "ai engineer summit prospects", "event prospecting", "scrape conference speakers", "who should I meet at".

browserbase/fetch

Use this skill when the user wants to retrieve a URL without a full browser session: fetch HTML or JSON from static pages, inspect status codes or headers, follow redirects, or get page source for simple scraping. Prefer it over a browser when JavaScript rendering and page interaction are not needed. Supports proxies and redirect control.

browserbase/functions

Deploy serverless browser automation as cloud functions using Browserbase. Use when the user wants to deploy browser automation to run on a schedule or cron, create a webhook endpoint for browser tasks, run automation in the cloud instead of locally, or asks about Browserbase Functions.

browserbase/safe-browser

Build local constrained-browser agents with a safe_browser tool that owns CDP, enforces a domain allowlist with Fetch interception, and lets a runtime Claude Agent SDK agent complete browsing tasks without raw browser, shell, or CDP access. Use when the user wants an agent to browse or scrape while staying on approved domains, demo blocked off-domain navigation, or generate a safe browser client.

Skills associés

steipete/sag

ElevenLabs text-to-speech with mac-style say UX.

community

steipete/oracle

Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.

community

steipete/peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

community

mattpocock/design-an-interface

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

community

mattpocock/prototype

Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

community

mattpocock/grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

community