Loading...
Loading...
Found 78 Skills
Lambdatest integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lambdatest data.
Verify UI changes in the browser using Shiplight MCP tools.
Set up Playwright end-to-end testing in a project, including test configuration, example tests, and CI integration.
E2E testing with Playwright - Page Objects, cross-browser, CI/CD
Complete browser automation with Playwright. **ALWAYS use when user needs browser testing, E2E testing, screenshots, form testing, or responsive design validation.** Auto-detects dev servers, saves test scripts to working directory. Examples - "test this page", "take screenshots of responsive design", "test login flow", "check for broken links", "validate form submission".
Diff-aware AI browser testing — analyzes git changes, generates targeted test plans, and executes them via agent-browser. Reads git diff to determine what changed, maps changes to affected pages via route map, generates a test plan scoped to the diff, and runs it with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, running regression checks on changed components, or validating that recent code changes don't break the user-facing experience.
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.
Create and manage monitoring checks using the Checkly CLI. Use when working with API checks, browser checks, URL monitors, Playwright checks, heartbeat monitors, alert channels, dashboards, or status pages.
Headless browser testing via persistent Bun.WebView session. Use when testing frontend UI, verifying page content, filling forms, clicking buttons, taking screenshots, or interacting with local or staging web applications. Triggers on phrases like "test the page", "check the UI", "browse to", "fill the form", "click the button", "take a screenshot".
Drive the running app in a real browser to prove a flow works — on demand, or as a saved test for the few flows worth re-running. Use when a multi-step flow needs checking end to end, right after deploying (against the live URL, not localhost), when the builder asks for Playwright, e2e or browser tests, and when something works locally but is reported broken in production. Also use before demo day to confirm the core action still works and to capture screenshots.
Builds a finished, polished static website from a short multiple-choice interview, checks it in a real browser, and publishes it. Use when someone wants a new website, homepage, portfolio, personal site, landing page, one-pager, small-business site, event or launch page, or says "make me a site". Also for changing a site it made before (new hours, prices, events, text, photos) and for redesigning an existing site, including when someone says theirs looks dated, generic or AI-made. Not for design advice alone, WordPress or Next.js projects, web apps, or themes.
Toggle between light and dark mode in Cursor's browser, screenshot both states, and flag missing token mappings or contrast issues.