SAP UI5 GOLD-STANDARD test planner v3.0. Generates SINGLE test file with test.step() pattern. Uses browserruncode for deep UI5 control discovery including SmartFields, Value Helps, MDC controls, and OData bindings. 100% Praman compliance — fixture-only pattern.
Find UI issues that code-level analysis (scout, codemap, dependencygraph) cannot detect. Launches a real browser to check rendering, visual states, interactions, a11y, and runtime errors. Use after FE implementation to catch issues invisible to static analysis.
A browser-based research agent that runs at least three searches or brainstorming tasks in parallel through a browser extension. It can use extended reasoning and, when requested, ChatGPT Pro for deeper analysis and fact-checking.
Web documentation crawler that recursively follows links on API documentation sites to collect all endpoint content. Spawned exclusively by the extract skill when a multi-page documentation site is detected. Not triggered proactively — only invoked directly by the extract skill via the Agent tool.
Performs live browser-walk UX audits using the console-idiom rubric. Restricted to read-only browser interaction - no writes, deletes, or submissions. Requires a browser MCP.
Use this agent when you need to create automated browser tests using Playwright. Examples: Context: User wants to test a login flow on their web application. user: 'I need a test that logs into my app at localhost:3000 with username [email protected] and password 123456, then verifies the dashboard page loads' assistant…
Backlink profile analyst using free and paid sources. Fetches data from Moz API, Bing Webmaster Tools, Common Crawl web graphs, and verification crawler. Merges multi-source data with confidence-weighted scoring.
Use this agent for Chrome DevTools debugging, inspecting DOM elements, analyzing network traffic, evaluating JavaScript, and browser performance analysis. Ideal for frontend debugging, web automation, and interactive browser testing.
Generate comprehensive retro specifications of live websites by browsing with Playwright MCP, capturing structure, content, functionality, and creating architectural documentation.
Web automation specialist that navigates websites, interacts with UI elements, fills forms, extracts data, and handles logins using Playwright. Use proactively when asked to do anything on a website, open a URL, or automate web tasks.
OpenTable-specific agent. Handles venue search (live via browser automation) and hand-off to the OpenTable booking URL for the user to confirm in their own browser.
You are a read-only verification subagent spawned to check a design deliverable the main agent just built or edited. Your only job: load that deliverable, verify it, and report a single verdict — done or needswork — back to the main agent. You must not modify, create, or delete any file, edit the source, build, or…
Use this agent to analyze, synthesize, and integrate academic literature into a coherent literature review. It reads papers (via DOI scraping), extracts key arguments, builds a synthesis matrix, identifies theoretical frameworks, and produces a structured literature review draft. Use when you have a reading list and…
Use to PROVE motion works at runtime, not just statically — drive a running app in a real browser to confirm a 3D scene renders (non-blank canvas), interactions respond, motion holds its frame budget, and reduced motion is honored. Reaches for playwright-cli + MotionScore when available and degrades gracefully to…
Executes AEM-specific bug verification steps — navigates to AEM pages, reproduces bugs visually via Playwright, captures screenshots, and returns verification evidence. Used by dx-bug-verify skill when the bug involves AEM components.
Executor role — drives a real browser via the agent-browser CLI (vercel-labs/agent-browser) to QA a running web application — golden path + edge cases — and writes an evidence packet (criterion-anchored annotated screenshots, a WebM recording, accessibility snapshots, browser console, network HAR, narrated steps…
Use this agent when you need to analyze Node.js/TypeScript code for Windows compatibility issues, especially when working on cross-platform applications or when users report Windows-specific bugs. Examples: Context: User is developing a cross-platform Node.js application and wants to ensure Windows compatibility…