Automate browser flows with Playwright, video recording, and API mocking.
npx skills add https://github.com/vanducng/skills --skill agent-browser-vanducng
Please help me install this Agent Skill. Skill: agent-browser Source: https://github.com/vanducng/skills/tree/main/skills/agent-browser Command: npx skills add https://github.com/vanducng/skills --skill agent-browser-vanducng
In environments where you need to drive complex browser tasks with built-in waiting semantics, this skill automates browsers by providing a Playwright-based driver with video recording, network mocking, and device emulation to deliver repeatable, observable flows.
Open your browser automation workflow by installing the agent-browser CLI and starting a recording-enabled session.
High-intent search queries and answers about installing and using this skill.
You record end-to-end browser automation flows as video using a Playwright-based driver that captures WebM video evidence during execution. This provides observable, repeatable flows for UI verification and issue reproduction by recording the session.
Network mocking in browser automation intercepts and blocks network requests to test UI under controlled conditions. You need it to simulate API responses, isolate frontend behavior, and reproduce specific error states reliably without relying on live backend services.
Set up Playwright to automate browser tasks with device emulation by installing the automation CLI globally and running an initial install to fetch Chromium. This enables device emulation alongside built-in waiting semantics for realistic browser interactions.
This browser automation approach works with profile and CDP modes, but requires awareness of their specific constraints. You must understand profile vs CDP mode limitations when configuring sessions to ensure repeatable browser-driven flows execute correctly.
The best way to capture a failing UI flow with mocked APIs is using a Playwright-based driver that combines video recording with network route mocking. This records the exact failure as saved video evidence while controlling the API responses to reproduce the issue.
You use Playwright waiting semantics for browser automation scripts to handle dynamic content loading and ensure realistic interactions. Built-in waiting prevents race conditions by automatically waiting for elements to be actionable before executing commands.
ryankoleanAutomate browser interactions and end-to-end tests across Chromium, Firefox, and WebKit.
47thtechcornerRecord browser interactions into video files using Playwright and FFmpeg.
linaproaiAutomate browser interactions and generate Playwright test code via CLI.
jiunbaeAutomate browser tasks for screenshots, scraping, form automation, and E2E tests.
