2.1K skills · sorted by relevance
Look up an Amazon product by ASIN, its unique product identifier, to retrieve the featured purchase offer, seller, price, availability, and fulfillment method. Compare other sellers' prices, shipping fees, and ratings in structured results.
Search for social media profiles associated with a person, brand, or business across platforms including Facebook, Twitter, Instagram, LinkedIn, and TikTok. Receive a downloadable CSV with profile links, follower counts, page titles, and description snippets.
Collect Google Maps reviews through BrowserAct using search keywords, language, and country settings. Retrieve reviewer names, ratings, review text, dates, and likes as structured data for reputation research, competitor comparisons, and customer feedback analysis.
Research Amazon best-selling products by keyword and regional marketplace. Collect structured product details, including prices, ratings, review counts, past-month sales, availability, and promotions, to compare competitors and investigate product markets.
Look up Amazon products using an ASIN, Amazon's unique product identifier. Retrieve structured details such as title, current price, ratings, brand, description, and material to enrich product catalogs or support price and rating comparisons.
Collect business information from Google Maps using search keywords, language, and a country preference. Retrieve names, addresses, phone numbers, websites, ratings, and operating status for local market research or sales lead lists.
Find public professional profiles by industry, job title, and website using the BrowserAct API. Collect names, profile links, biographies, and company affiliations to build prospect lists, identify recruiting targets, or research key people at competitors.
Test local web applications with Python scripts using Playwright, a browser automation tool. Verify interface behavior, investigate problems, capture screenshots, and inspect browser logs, with a helper that manages one or more application servers.
Automate web tasks in an already-running Chrome session, including clicks, forms, and content extraction from signed-in pages. Use screenshots to guide actions and verify visible results, with remote browsers available for isolated work.
Retrieve pages blocked by web access filters, read Chinese and social platforms through dedicated tools, and inspect archived copies with their dates. Escalate to browser interaction when simpler extraction methods cannot provide the needed content.
Test changed screens or explore an entire app in a real browser. Check interactions, accessibility, and mobile layouts, then document failures with screenshots, reproduction steps, expected results, and suggested fixes.
Use when the user types /agentlas-browser <url-or-query>, /agentlas browser, or /hep-browser for browser-required tasks, rendering pages, form flows, or visual evidence.
The English summary is being prepared. Showing the original description.
Run the pre-flight checklist before an agent drives a browser — the untrusted-web-content threat (every page is attacker-controllable), the credential and session-cookie exposure, the action-confirmation gates for purchases and posts, and the sandboxing that limits the damage. Use when asked let my agent browse safely, is it safe to give the agent computer/browser use, guardrails before the agent uses my browser, or review my browser agent's setup. Produces the sandbox decision, the content-injection defenses, the action gates, and the credential-isolation rules.
The English summary is being prepared. Showing the original description.
Build alternative browser engines using BrowserEngineKit. Use when developing a non-WebKit browser engine for iOS/iPadOS in supported regions, managing web content/rendering/networking extension processes, configuring GPU and networking process capabilities, checking alternative-engine device eligibility, or reviewing BrowserEngineKit entitlements and Info.plist setup.
The English summary is being prepared. Showing the original description.
Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
The English summary is being prepared. Showing the original description.
Connects to Oxylabs remote agent browsers over the Chrome DevTools Protocol (CDP) with Playwright or Puppeteer. Managed browser environment, residential proxies, geo-targeting, persistent sessions and profiles, session recording and live VNC inspection for debugging. Use instead of WebFetch or a local browser whenever a site renders with JavaScript, serves access challenges, verification interstitials or bot-management block pages, or needs a full browser session, screenshots or PDFs. Covers connection, retries, error recovery, built-in challenge handling (the page_handler parameter, the oxylabs-page-status page state reported by the page handler, manual triggering), telling a handled challenge from a block that needs a fresh identity, and reliable access to publicly available data without manual intervention.
The English summary is being prepared. Showing the original description.
Direct browser control via the Browser Use Terminal CLI. Use when the user wants to automate, scrape, test, or interact with web pages — you drive the browser yourself with Python helpers.
The English summary is being prepared. Showing the original description.
Drive Chrome via the DevTools Protocol from JavaScript. Run JS snippets through the `browser-harness-js` CLI — it auto-spawns a long-lived bun HTTP server holding a fully-typed CDP `Session`, and every call (`browser-harness-js 'await session.Page.navigate(...)'`) executes against the same persistent connection. Session, active target, and globals survive across calls. Use when the user wants to automate, script, or inspect a Chrome browser via CDP — single tab or multi-tab, attach to existing Chrome or to a new one launched with --remote-debugging-port.
The English summary is being prepared. Showing the original description.
Goal-driven E2E testing where a browser agent (Playwright MCP / computer-use) reads a natural-language goal and explores the app via the accessibility tree to assert outcomes — no pre-written script. Covers when intent-driven beats scripted, making agent runs repeatable and bounded (pinned model, temperature 0, seeded data, bounded steps, explicit success assertion, snapshot-not-pixel), cost/latency control, the accessibility-tree-first interaction model, CI gating, and graduating a stable run into a scripted Playwright test. Use when: "agentic browser test," "goal-driven browser test," "let an agent explore the app," "natural-language E2E," "browser agent smoke test," "Playwright MCP test." Not for: Writing/maintaining deterministic scripted Playwright tests — that is playwright-automation. Testing your product's OWN LLM features — that is ai-system-testing. Related: playwright-automation, ai-system-testing, exploratory-testing, test-reliability, qa-project-context.
The English summary is being prepared. Showing the original description.
Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
The English summary is being prepared. Showing the original description.
Hoyeon browser automation workflow for Codex. Use when the user invokes "$hoyeon-browser-work" or asks Codex to perform a browser task through recon-first chromux automation. This adapter loads the canonical browser-work skill and follows its Codex runtime surface.
The English summary is being prepared. Showing the original description.
Recon-first browser automation. Orchestrator explores the site first via chromux, saves a guide file with insights, then delegates execution to browser-explorer agent. Use when: "/browser-work", "브라우저 작업", "사이트에서 해줘", "웹에서 해줘", "LinkedIn에서", "크롬으로", "browser task", "automate this site".
The English summary is being prepared. Showing the original description.
Browser automation CLI for AI agents. Use when needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. TRIGGER when user requests to "open a website", "fill out a form", "click a button", "take a screenshot", "debug this in browser", "scrape data from a page", "test this web app", "login to a site", "frontend UI/UX aesthetics", "automate browser actions", or any task requiring programmatic web interaction.
The English summary is being prepared. Showing the original description.
Browser automation for AI agents using the agent-browser CLI and Playwright. Use when navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging into sites, or automating any browser task. Triggers on "open a website", "fill out a form", "click a button", "scrape data", "test this web app", "automate browser actions", or any programmatic web interaction request.
The English summary is being prepared. Showing the original description.