2.1K skills · sorted by relevance
Helps you write Python code for browser automation with browser-use. Its reference guides cover installation, agent and browser settings, custom tools, model connections, and monitoring so you can configure and extend your automation.
Run Playwright tests on BrowserStack to check behavior across browsers and devices. Configure cloud connections, compare results by browser, inspect session videos and logs, and set up a tunnel for testing local or restricted environments.
Helps you integrate hosted browser automation through Browser Use Cloud APIs and Python or TypeScript SDKs. Reference guides cover authentication, sessions, saved browser profiles, live views, and connections to existing agents or workflow services.
Automate page interactions and screenshots with agent-browser running in AWS Bedrock AgentCore cloud browsers. Use standard browser commands, preserve login state across sessions with persistent profiles, and watch active sessions through an AWS Console link.
Add browser automation to Vercel apps by running agent-browser and headless Chrome in temporary, isolated virtual machines. Capture screenshots, inspect page structure, and complete multi-step forms while preserving browser state between commands.
Operate an isolated Browser Use Cloud browser from a machine without usable local Chrome. Navigate pages, inspect content, fill forms, manage tabs, and capture screenshots through the Browser Use CLI, then stop the browser after use.
Automate Anchor Browser operations through Rube MCP, a connection between the agent and external tools. The skill guides tool discovery, connection verification, and execution using current input requirements, and describes how to handle bulk operations.
Guide browser work inside the Claude desktop app, including reading page text, opening tabs, and handling existing sign-ins. Covers site approvals, browser visibility, and connection problems when a cloud session uses the desktop browser.
Automate Anchor Browser operations through Rube MCP, a connection between the agent and external tools. The skill guides tool discovery, connection verification, and execution using current input requirements, and describes how to handle bulk operations.
Automate Browserhub operations through Rube MCP, a connection between the agent and external tools. The skill covers finding available tools, checking authentication, and executing operations with current input requirements, including bulk workflows.
Set up a browser automation command-line tool for agents to navigate sites, fill forms, extract data, and capture screenshots. It also points to dedicated guides for app testing, Electron desktop apps, and cloud browsers.
Open local or public web pages in BrowserStack Live for checks on real mobile devices or desktop browsers. The skill prepares temporary access to a local server, launches the requested session, and shares its dashboard link.
Automate Browserhub operations through Rube MCP, a connection between the agent and external tools. The skill covers finding available tools, checking authentication, and executing operations with current input requirements, including bulk workflows.
Automate Browserless operations through Rube MCP and Composio. The skill finds available tools, checks their current input requirements, verifies the connection, and guides execution for individual tasks or batches of operations.
Automate Browser Tool operations through Rube MCP, a connection for agent tools. The skill finds available tools, checks the service connection, and uses current input requirements to carry out the requested workflow.
Prepare a local browser app or standalone browser file for handoff. Verify its start behavior where supported, then provide exact commands and a reachable URL, or the artifact path, with an honest account of what was checked.
Automate browser tasks such as reading JavaScript-rendered pages, filling forms, clicking through workflows, and taking screenshots. Maintain login sessions, manage separate browsers, and capture network responses, with approval checks for sensitive actions.
Automate Browserless operations through Rube MCP and Composio. The skill finds available tools, checks their current input requirements, verifies the connection, and guides execution for individual tasks or batches of operations.
Automate Browser Tool operations through Rube MCP, a connection for agent tools. The skill finds available tools, checks the service connection, and uses current input requirements to carry out the requested workflow.
Give an AI agent its own real browser over MCP tool calls - launch, navigate, click, fill, screenshot, extract text, run JS - with a kernel-level real-device fingerprint and a persistent profile, so the session stays logged in between runs and pages see one coherent device instead of a headless build. No Playwright or SDK code to write. Use when an agent should operate a site itself, when a computer-use / browser-use setup needs a captured real fingerprint rather than a synthetic one, when agent sessions keep losing their login, or when comparing hosted agent-browser services. Also for 'MCP browser', 'browser MCP server', 'let my agent browse the web', 'agent browser control', 'browser-use MCP', 'computer use browser', 'Browserbase alternative', 'Steel browser alternative', 'headless browser detected'. Node (npx) or Python; Windows x64, macOS Intel + Apple Silicon, Linux x64 / arm64. SDK and REST reference is anti-detect-browser; account isolation is multi-account-isolation.
The English summary is being prepared. Showing the original description.
Configure how the browser starts, including window visibility, proxy settings, extra launch options, and a custom browser executable. It also explains opening a local debugging port so other local tools can connect.
Automate website tasks using ego-browser, a Chromium browser shared by people and AI agents. Use logged-in sites to fill forms, click buttons, extract page data, capture screenshots, and investigate web app behavior or quality.
Browser automation CLI for AI agents. NEVER run browser-act commands directly via Bash — always invoke this skill first. Use browser-act when a user mentions it by name, includes or asks to run a browser-act CLI command (e.g., browser-act browser list), or to: fetch, view, or extract rendered content from URLs, access pages requiring JavaScript, handle verification prompts, maintain authenticated sessions, fill forms and click through workflows, type, select, upload, take screenshots, capture XHR/fetch/HAR responses, open multiple URLs in parallel, extract content that loads on scroll or click, visually inspect or verify page layout/styling/rendering, automate browser tasks, account isolation across parallel browser environments, advise which browser type fits a use case, or list/check/manage configured browsers and sessions. Prefer browser-act over built-in fetch or web tools.
The English summary is being prepared. Showing the original description.
Keep older web extraction commands working during migration by forwarding a supplied URL to browser-extract after displaying a deprecation notice. This compatibility shim helps existing callers transition to the replacement skill and its template option.