Browser automation CLI for AI agents. Use when the user needs to inspect, test, or automate browser behavior: navigating pages, filling forms, clicking buttons, taking screenshots, extracting page…
Extract structured data via stored browser-templates or one-shot DOM queries, with mandatory AIDefence PII + prompt-injection gates before…
DEPRECATED in v0.2.0 -- use browser-extract instead; this is a thin shim for backward compatibility, removed in v0.3.0
Fill a web form by mapping field-name → value, with optional template lookup from browser-templates for known forms
Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features.
Orchestrate multi-phase deep research with web search, memory retrieval, pattern matching, and synthesis into structured findings
Capture full-page screenshots of web pages via Chrome DevTools Protocol with zero dependencies. Useful for portfolios, case studies, and audit reports.
Complete browser automation with Playwright.
Browser automation via Playwriter (remorses) using persistent Chrome sessions and the full Playwright Page API.
Control the user own Chrome browser via Playwriter extension with Playwright code snippets in a stateful local js sandbox.
Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating…
Automate browser interactions, test web pages and work with Playwright tests.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol.
Browser automation using Vercel's agent-browser CLI.
Web browser automation with AI-optimized snapshots for claude-flow agents
Controls a local browser from a sandboxed remote machine.
Automates browser interactions for form filling and web page interaction.
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts.
Automate Customjs tasks via Rube MCP (Composio).
Activate when the user needs to interact with any website — browser automation, web scraping, screenshots, form filling, UI testing…
Web, Search & Scraping agent skills on mcprush shape how an agent reads and quotes what it finds, so an answer arrives with the source attached rather than with a confident paraphrase of one. The kinds are workflow, expertise, output format, voice & style and guardrail, and the one a skill belongs to is the fastest way to guess what it will do to your prompt.
What to look at before installing one is what it costs in context and what it takes away: a guardrail that refuses an action and a voice that rewrites a sentence are both skills, and only one of them will stop the agent doing something. Every skill here says which kind it is, what it costs in context, what it needs beside it to work and the licence it is published under, next to the publisher it came from and whether that publisher has been verified. The filters on the left narrow it further and the sort at the top decides what comes first.
A skill is not connected to anything: there is no endpoint to authorise and nothing routed through the gateway. Installing one drops a folder of instructions into the client’s own skill folder, and uninstalling it is deleting that folder. The exact line for each client is on the skill’s own page, because it differs by client rather than by skill.