Results for “browser”

Read this skill before the first step that uses Claude in Chrome, the browser extension whose tools are named mcp__claude-in-chrome__* (also called Chrome, the browser extension, or the external browser) and which acts in the person's real Chrome with their own sign-ins; before those tools are turned on there may be a single enable__mcp__claude-in-chrome tool instead. It covers loading the tools in one ToolSearch call, checking the person's open tabs and working in a new tab, site permissions, GIF recordings, console logs, dialogs to avoid, and when to stop and ask. It is not for the built-in browser (mcp__Claude_Browser__* or mcp__remote-devices__Claude_Browser__* tools), which has its own skill, and it does not decide which browser to use.

The English summary is being prepared. Showing the original description.

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. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

The English summary is being prepared. Showing the original description.

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. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

The English summary is being prepared. Showing the original description.

Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation. Use this skill whenever the user needs help with the Cloud REST API (v2 or v3), browser-use-sdk (Python or TypeScript), X-Browser-Use-API-Key authentication, cloud sessions, browser profiles, profile sync, CDP WebSocket connections, stealth browsers, residential proxies, CAPTCHA handling, webhooks, workspaces, skills marketplace, liveUrl streaming, pricing, or integration patterns (chat UI, subagent, adding browser tools to existing agents). Also trigger for questions about n8n/Make/Zapier integration, Playwright/ Puppeteer/Selenium on cloud infrastructure, or 1Password vault integration. Do NOT use this for the open-source Python library (Agent, Browser, Tools config) — use the open-source skill instead.

The English summary is being prepared. Showing the original description.

Computer Use Agent — autonomous browser control via Steel, Browser Use, and Browserbase cloud providers. Supports headful CDP sessions, CAPTCHA solving, proxy rotation, live view, session recording/replay, Playwright/Puppeteer integration, and LLM-driven visual browsing. Use when asked about computer use, browser automation, web scraping, Steel sessions, cloud browsers, headful browsing, CAPTCHA solving, or autonomous web navigation.

The English summary is being prepared. Showing the original description.

Read this skill before the first step that uses Claude in Chrome, the browser extension whose tools are named mcp__claude-in-chrome__* (also called Chrome, the browser extension, or the external browser) and which acts in the person's real Chrome with their own sign-ins; before those tools are turned on there may be a single enable__mcp__claude-in-chrome tool instead. It covers loading the tools in one ToolSearch call, checking the person's open tabs and working in a new tab, site permissions, GIF recordings, console logs, dialogs to avoid, and when to stop and ask. It is not for the built-in browser (mcp__Claude_Browser__* or mcp__remote-devices__Claude_Browser__* tools), which has its own skill, and it does not decide which browser to use.

The English summary is being prepared. Showing the original description.

Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

The English summary is being prepared. Showing the original description.

Use Browser Use cloud API to spin up cloud browsers for Clawdbot and run autonomous browser tasks. Primary use is creating browser sessions with profiles (persisted logins/cookies) that Clawdbot can control. Secondary use is running task subagents for fast autonomous browser automation. Docs at docs.browser-use.com and docs.cloud.browser-use.com.

The English summary is being prepared. Showing the original description.

Review Storybook's minimum supported browser versions using Plausible documentation traffic data. The skill presents usage evidence and proposed versions for approval, then updates pinned settings and documentation and opens a pull request with the recorded decision.

• Review minimum browser versions using documentation traffic
• Compare browser version shares and approve support floors
• Update browser settings and migration documentation together

Describe browser actions in everyday language and let page-agent carry them out. Useful when page elements are hard to identify reliably, with a fallback to direct element-based browser tools if the natural-language setup is unavailable.

• Clicking a button described in everyday language
• Entering a search term and submitting the form
• Interacting with pages whose element identifiers change

Complete a website login, including interactive multi-factor authentication, and store an opaque reference to session credentials. Prepares authentication for later browser tasks while keeping raw cookie values out of model context and stored records.

• Preparing login for repeated visits to a website
• Refreshing an expired session record
• Completing a login with multi-factor authentication

Test interface behavior in a real browser and save actions, checks, and screenshots in a replayable RVF session file. Use recorded sessions to repeat tests, investigate CI failures, and compare screenshots against an earlier baseline.

• Checking user flows in a real browser
• Recording a baseline before interface changes
• Comparing screenshots with a previous test run

Automate forms, clicks, screenshots, and website checks in a browser where you are already signed in. A separately launched browser also supports scraping and network capture, while login or verification steps can be handed to a person.

• Fill forms on websites where you are already signed in
• Capture screenshots and check website behavior
• Record network traffic in a separately launched browser

Review which actions are available in each of four Remotion Studio modes. Use these distinctions when implementing or checking interface controls, so actions that depend on a server are hidden or disabled where the mode cannot support them.

• Check mode support before adding a Studio action
• Review controls in a deployed Studio
• Check behavior after the preview server disconnects

Automate Electron desktop apps with agent-browser through CDP, a browser debugging connection. Click controls, enter text, extract content, and capture screenshots while switching between app windows or embedded pages for routine work and testing.

• Automating clicks and form entry in desktop apps
• Extracting text and screen information from apps
• Capturing screenshots for application testing

Use QwenPaw's built-in Browser SDK, a browser control interface, to read pages, search, fill forms, click controls, and capture screenshots through asynchronous Python. The workflow checks the page before and after actions and hands authentication steps to a person.

• Search a website and inspect the resulting page
• Fill forms and select options in a browser
• Read page text and capture screenshots

Automate browser tasks through BrowserWing's HTTP API, from navigation and form filling to extracting search results. Inspect page structure to identify controls, capture screenshots, and run multiple actions in sequence.

• Filling and submitting web forms
• Extracting search results and links
• Capturing screenshots and inspecting page structure

Use the bsk command-line tool and browser extension to automate logged-in Chromium. Read pages, complete forms, export tables or lists as JSON or CSV, manage tabs, test interfaces, and investigate website failures.

• Reading pages with an existing browser login
• Exporting tables or lists as JSON or CSV
• Filling forms and managing browser tabs

Automate website interactions through a command-line browser tool. Navigate pages, fill forms, extract text, save screenshots or PDFs, reuse login sessions, and compare page states to check the effects of actions or website changes.

• Automating form entry and submission
• Extracting page text and saving screenshots
• Comparing page appearance before and after changes

Automate Chrome using an existing login session through CDP, Chrome’s remote control interface. Open pages, click elements, enter text, extract page content, run JavaScript, and inspect authentication tokens with agent-browser.

• Automating tasks on sites where you are already signed in
• Extracting text from web pages
• Clicking buttons and filling in forms

Browser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, log into sites, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", "open the browser", or any browser interaction request.

The English summary is being prepared. Showing the original description.

Browser automation platform with 78 built-in scripts and full CLI. Turn any website into structured data with one command. Use when the user needs to scrape websites, extract data, automate browsers, run built-in scripts (Hacker News, GitHub trending, Bilibili, Zhihu, stock data, etc.), navigate pages, fill forms, take screenshots, or control Chrome programmatically. Triggers include "scrape", "extract data", "browser automation", "web data", "trending", "hot topics", "stock data", "run script", "open website", "fill form", "screenshot", "headless browser".

The English summary is being prepared. Showing the original description.

Use ONLY when calling the `browser_execute` tool or driving a real browser via the Chrome DevTools Protocol. Required reading before the first `browser_execute` call in a session. Covers the three connection methods (local Chrome with remote debugging, isolated debug-port profile, Browser Use cloud), the in-process `session` / `console` snippet model, attaching to a page target, common CDP commands, the per-project `.bcode/agent-workspace/` for reusable scripts, and screenshot auto-attachment.

The English summary is being prepared. Showing the original description.

Browser Use — direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers hosted cloud browsers for AI agents: the browser-use Python library (Browser(use_cloud=True)), Playwright, Puppeteer or any CDP client.

The English summary is being prepared. Showing the original description.