2.1천건 · 관련도순
Collect Amazon product reviews by supplying an ASIN, Amazon's product identifier. BrowserAct returns ratings, review text, publication dates, reviewer details, and verified purchase status without an Amazon login, providing data for feedback research and competitor comparisons.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explore how a website provides data or handles actions, then turn verified methods into a reusable Skill package with SKILL.md and Python scripts. The workflow includes testing, installation, and execution when requested.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Find GitHub projects using keywords, minimum stars, and update dates, then collect repository details and contributor profiles through BrowserAct. Results include project descriptions, contributor biographies, personal websites, and Twitter handles for research, recruiting, or collaboration scouting.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Automates website navigation, form entry, and information extraction through browser commands. Helps test web applications, reuse saved login state, and capture screenshots, PDFs, or recordings of browser workflows for inspection and documentation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Kimi Browser Extension（Kimi 浏览器扩展，原 Kimi WebBridge）lets AI control the user's real browser — navigate, click, type, read, screenshot, and interact with any website using the user's actual login sessions. Use this skill whenever the user wants to interact with websites, automate browser tasks, scrape web content, or perform any action requiring a real browser. Also use when the user mentions "browser", "webpage", "open URL", "screenshot", asks to read/interact with any website, or wants a reusable CLI tool or script that automates a specific website. Use even for simple-sounding browser requests — the daemon handles all complexity.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Browser Use is an open-source Python library that lets an LLM agent drive a real browser to navigate sites, fill forms, click and extract data from a plain-English task. Use when the user wants an AI agent to automate a website, scrape pages that need clicking or login, return structured data from the web, add browser tools to a coding agent, or run browser agents locally or in the cloud.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns. This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping, and agentic browser control. Key insight: Playwright won the framework war. Unless you need Puppeteer's stealth ecosystem or are Chrome-only, Playwright is the better choice in 2025. Critical distinction: Testing automation (predictable apps you control) vs scraping/agent automation (unpredictable sites that fight back). Different problems, different solutions. Use when "playwright, puppeteer, browser automation, headless, web scraping, e2e test, end-to-end, selenium, chromium, browser test, page.click, locator, playwright, puppeteer, browser, automation, testing, scraping, headless, e2e, selenium, web-testing" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user explicitly wants to connect to a running Chrome browser, scan local CDP ports, specify a `cdp_port`, or share a single browser across multiple agents/tools. By default, browser_use already launches the browser using managed CDP; if the user does not want to expose browser history, cookies, or other sensitive data, recommend using `private_mode=true` instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to: - Navigate websites and interact with web pages - Fill forms and click buttons - Take screenshots of web content - Test web applications - Extract information from web pages - Debug frontend issues in the browser - Monitor console logs and network requests - Record browser sessions as video This skill uses agent-browser for comprehensive browser automation. RECOMMENDATION: Disable Chrome DevTools or Playwright MCP when using this skill to save context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Browser Use is an open source browser automation framework for AI agents that turns websites into controllable interfaces for multi-step tasks. It combines a Python SDK, browser orchestration, and model integrations so agents can navigate, extract data, and complete workflows in real browsers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Browserbase when an agent needs hosted browser sessions, remote automation, session recording, and scalable browser infrastructure without managing Chromium fleets directly. This skill packages the Browserbase API and SDK into a concrete workflow for running, monitoring, and extracting results from cloud browser sessions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Browserbase MCP Server gives agents cloud browser control through Browserbase and Stagehand, with both hosted HTTP and self-hosted stdio options. It suits teams that want MCP-based browser automation but prefer Browserbase sessions and Stagehand’s action model instead of running Playwright locally.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Browserable is an open-source, self-hostable browser automation library built for AI agents. This skill turns Browserable into a repeatable workflow for navigation, form filling, extraction, and browser-based task execution with local control instead of a hosted black box.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pythinker Browser Extension lets AI control the user's real browser — navigate, click, type, read, screenshot, and interact with any website using the user's actual login sessions. Use this skill whenever the user wants to interact with websites, automate browser tasks, scrape web content, or perform any action requiring a real browser. Also use when the user mentions "browser", "webpage", "open URL", "screenshot", or asks to read/interact with any website. Use even for simple-sounding browser requests — the daemon handles all complexity.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browser_use, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle hooks, MCP server setup, or monitoring/observability with Laminar or OpenLIT. Also trigger for questions about browser-use installation, prompting strategies, or sensitive data handling. Do NOT use this for Cloud API/SDK usage or pricing — use the cloud skill instead. Do NOT use this for directly automating a browser via CLI commands — use the browser-use skill instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Direct browser control via CDP — use for any task involving a website or web app: browsing, scraping and data extraction, filling forms, testing sites, taking screenshots, automating web workflows. Also covers hosted cloud browsers for AI agents: the browser-use Python library (Browser(use_cloud=True)), Playwright, Puppeteer or any CDP client.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify that browser profiles are actually isolated from one another instead of assuming it - confirm each profile's timezone agrees with its own exit IP, that WebRTC exposes only the proxy, that canvas and WebGL hashes stay identical across relaunches of one profile, and that no two profiles share a persona, a cookie jar, or an address. Use when several of your own accounts or test identities run from one machine and the setup needs checking, when a profile tested clean but something still looks off, when choosing which detection suites to run (CreepJS, whoer, browserleaks WebRTC, pixelscan, liarjs), when auditing what a vendor runtime does with API and proxy credentials, or when asking which layers browser isolation cannot cover at all. Also for 'profile isolation check', 'fingerprint consistency test', 'timezone mismatch', 'WebRTC leak', 'canvas hash unstable', 'account association', 'temporary profile', '防关联', '多账号', '隔离自检'. The SDK is anti-detect-browser; MCP is browser-mcp-agent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Target a specific Google Chrome user profile for browser automation via CDP. Discovers installed profiles from the Chrome Local State file, launches Chrome with the requested profile attached to a debug port, and connects agent-browser via `agent-browser connect <port>`. Use when "automate using my Work/Personal Chrome", "open site with my saved session", or "use Chrome profile named <name>". NOT for headless scraping without an existing user profile (use mk:agent-browser directly); NOT for importing cookies only (use agent-browser --auto-connect state save).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Default to Firefox for browser automation and decide when Chrome is truly required. Use before any task that needs a browser: fetching a page, grabbing cookies, headless runs, logging into a site. Includes a matrix of which tasks must stay on Chromium and why. Triggers: /firefox, /ff, via firefox, need a browser, headless browser, which browser to use, browser automation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Browserstack — browserStack cloud testing platform monitoring and analysis. Covers Automate session management, live testing status, App Automate tracking, build and session analysis, device/browser usage metrics, and account quota monitoring. Use when managing BrowserStack test sessions, reviewing cross-browser results, or monitoring cloud testing infrastructure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.