Use when the user wants extremely fast browser automation via fast-browser-use / fbu, especially for DOM-heavy pages, fast extraction, or browser tasks on macOS/Linux with Chrome installed.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Use when the user wants extremely fast browser automation via fast-browser-use / fbu, especially for DOM-heavy pages, fast extraction, or browser tasks on macOS/Linux with Chrome installed.
displayName
Fastest Browser Use
emoji
⚡
summary
Rust-powered browser automation that rips through DOMs 10x faster than Puppeteer.
{"requiredEnv":["CHROME_PATH"],"example":"# Standard headless setup\nexport CHROME_PATH=\"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome\"\nexport BROWSER_HEADLESS=\"true\"\n"}
Fastest Browser Use
A Rust-based browser automation engine that provides a lightweight binary driving Chrome directly via CDP. It is optimized for token-efficient DOM extraction, robust session management, and speed.
⚠️ Important: Command Behavior
navigate is a one-shot command — it opens the page, completes, then immediately kills Chrome. Do NOT use it if the user wants to see/interact with the browser.
login keeps Chrome open and waits for user input (Enter) before saving session and closing. Use this when the user needs to interact manually.
--headless false shows the Chrome window on the user's desktop (requires X11/Wayland display). Use this when the user wants to watch operations.
--user-data-dir reuses an existing Chrome profile (login state, cookies, extensions). However, it may conflict if Chrome is already running with that profile. Prefer --load-session for saved sessions instead.
When you need to access a platform that requires the user's login (e.g. Polymarket, GitHub, Twitter), follow this complete workflow:
Session Persistence: --user-data-dir vs --load-session
--load-session only restores cookies. Many modern platforms (OAuth, wallet-based, SPA) store auth state in localStorage/IndexedDB, so cookies alone are insufficient.
--user-data-dir persists the entire Chrome profile (cookies + localStorage + IndexedDB + service workers). This is the recommended approach for most platforms.
Use a dedicated profile directory per platform (e.g. ~/.openclaw/chrome-profiles/polymarket/) to avoid lock conflicts with the user's running Chrome.
["Genode OS is a tool kit for building highly secure special-purpose OS","Mobile carriers can get your GPS location","Students using \"humanizer\" programs to beat accusations of cheating with AI","Finland to end \"uncontrolled human experiment\" with ban on youth social media",
...
]
Works on any infinite scroll page: Reddit, Twitter, LinkedIn feeds, search results, etc.
--analyze-structure: Also extract page structure (headings, nav, sections, meta)
--max-pages N: Limit structure analysis to N pages (default: 5)
--max-sitemaps N: Limit sitemap parsing to N sitemaps (default: 10, useful for large sites)
Example output:
{"base_url":"https://example.com","robots_txt":"User-agent: *\nSitemap: https://example.com/sitemap.xml","sitemaps":["https://example.com/sitemap.xml"],"pages":["https://example.com/about","https://example.com/products","https://example.com/contact"],"page_structures":[{"url":"https://example.com","title":"Example - Home","headings":[{"level":1,"text":"Welcome to Example"},{"level":2,"text":"Our Services"}],"nav_links":[{"text":"About","href":"/about"},{"text":"Products","href":"/products"}],"sections":[{"tag":"main","id":"content","role":"main"},{"tag":"footer","id":"footer","role":null}],"main_content":{"tag":"main","id":"content","word_count":450},"meta":{"description":"Example company homepage","canonical":"https://example.com/"}}]}
Use this to understand site architecture before scraping, map navigation flows, or audit SEO structure.
⚡ Performance Comparison
Feature
Fast Browser Use (Rust)
Puppeteer (Node)
Selenium (Java)
Startup Time
< 50ms
~800ms
~2500ms
Memory Footprint
15 MB
100 MB+
200 MB+
DOM Extract
Zero-Copy
JSON Serialize
Slow Bridge
Capabilities & Tools
Vision & Extraction
vision_map: Returns a screenshot overlay with numbered bounding boxes for all interactive elements.
snapshot: Capture the raw HTML snapshot (YAML/Markdown optimized for AI).
screenshot: Capture a visual image of the page.
extract: Get structured data from the DOM.
markdown: Convert the current page content to Markdown.
sitemap: Analyze site structure via robots.txt, sitemaps, and page semantic analysis.
Navigation & Lifecycle
navigate: Visit a specific URL.
go_back / go_forward: Traverse browser history.
wait: Pause execution or wait for specific conditions.
new_tab: Open a new browser tab.
switch_tab: Switch focus to a specific tab.
close_tab: Close the current or specified tab.
tab_list: List all open tabs.
close: Terminate the browser session.
Interaction
click: Click elements via CSS selectors or DOM indices.
input: Type text into fields.
press_key: Send specific keyboard events.
hover: Hover over elements.
scroll: Scroll the viewport.
select: Choose options in dropdowns.
State & Debugging
cookies: Manage session cookies (get/set).
local_storage: Manage local storage data.
debug: Access console logs and debug information.
Usage
This skill is specialized for complex web interactions that require maintaining state (like being logged in), handling dynamic JavaScript content, or managing multiple pages simultaneously. It offers higher performance and control compared to standard fetch-based tools.
