Results for “browser-automation”

Builds reliable browser automation skills by iteratively running a browsing task, reading the trace, and improving the navigation strategy until it passes consistently.

Automate browser tool operations through Composio's Browser Tool toolkit via Rube MCP, with tool discovery and connection management.

Use when an AI agent needs to control a browser, automate web tasks, scrape pages, fill forms, or click buttons autonomously. Triggers on: 'browser automation', 'web agent', 'browser-use', 'AI browse', 'tự động duyệt web', 'điều khiển trình duyệt', 'scrape with AI', 'click button automatically', 'fill form automatically', 'web task automation'.

Controls and inspects a live Chrome browser for automation, debugging, and performance profiling using the Chrome DevTools MCP server.

Official Puppeteer Model Context Protocol Server for browser automation.

Automate Cloudflare Browser Rendering tasks through Composio's toolkit via Rube MCP, with tool discovery and connection management.

Capture a full DevTools-protocol trace of any browser automation, bisect the stream into per-page searchable buckets, and attach a trace to an in-progress session for debugging.

Controls a Chrome browser through the AIPex extension and MCP bridge, enabling navigation, clicking, form filling, screenshots, tab management, and content downloads.

Provides isolated, agent-native sandboxes for code execution, live preview URLs, browser automation, and access to 50+ tools via CLI or HTTP, with no SDK or API keys required.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

A fast Rust-based headless browser automation CLI with Node.js fallback that enables AI agents to navigate, click, type, and snapshot pages via structured commands.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

Reuse a running Chrome session for browser automation via Playwriter CLI + MCP. Use when the task depends on the browser the user already has open — existing logins, cookies, extensions, passkey-friendly flows, or live-tab continuity. Route repeatable fresh-browser or CI-style checks to `browser-harness` instead.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

This skill enables comprehensive control and inspection of the Chrome browser without extensions, utilizing the Chrome DevTools Protocol via chrome-devtools-mcp. Use it for advanced browser automation, performance analysis, debugging network requests, taking screenshots, and interacting with web pages. Triggers include explicit requests to browse, automate, debug, or analyze Chrome's behavior, or any task requiring headless/direct browser interaction.

Extract official websites and social media profiles (LinkedIn, Facebook, X/Twitter, Instagram, YouTube, TikTok) from a company name or website URL using automated browser scripts.

Control a headless browser to navigate pages, click elements, fill forms, take screenshots, record video, and execute JavaScript using Playwright and inference.sh.

Bundles a prompt with selected files into a one-shot request for another model, supporting API and browser engines with session reattachment.

Automates filling in a Microsoft Forms form using Playwright MCP, with a review step before submission.

Automate Hyperbrowser operations through Composio's toolkit via Rube MCP, with dynamic tool discovery and connection management.

Generates images and conducts conversations through the Gemini website (gemini.google.com) using MCP tools, scripts, or a managed browser as a fallback.

Automate Browseai operations through Composio's Browseai toolkit via Rube MCP, including tool discovery, connection management, and execution.

Generates a Playwright test from a user-provided scenario by recording browser interactions via Playwright MCP, then saves and runs the test until it passes.

Explores websites using Playwright to identify core features and generate test cases.

Automate Apiflash screenshot and rendering tasks through Composio's Apiflash toolkit via Rube MCP.

将内容拆解为系列卡通风格信息图提示词，通过 Chrome DevTools MCP 自动化调用 Gemini web app 生成图片，并自动收集到本地临时目录。

Queries managed Google NotebookLM notebooks for citation-backed, source-grounded answers via local Claude Code browser automation; use for uploaded sources, not live web search.

Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and the browser embedded inside the Orca app. Use when the user says "$orca-cli", "use orca cli", "Orca worktree", "child worktree", "cardStatus", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "terminal send", "full handoff", "handover", "give this to another agent", "another worktree", "Orca browser", or "control the browser inside Orca". Prefer this over raw `git worktree`, ad hoc PTYs, Playwright, or Computer Use when the task touches Orca-managed state. Use Computer Use for browser windows, webviews, or desktop UI outside Orca's embedded browser.