القائمة
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Browser Use CLI 3.0 Python heredoc workflow.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Use whenever the user asks to build a web page, landing page, dashboard, form, or any frontend UI — whether from scratch or by redesigning an existing interface. Helps with aesthetic direction, typography, color palettes, layout, and making choices that don't read as templated defaults. Also trigger when the user says 'design a page', 'make a UI', 'build a frontend', 'redesign this', 'make it look good', or wants HTML/CSS for a visual interface.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions 'deck,' 'slides,' 'presentation,' or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Create new skills, modify and improve existing skills. Use when users want to create a skill from scratch, edit, or optimize an existing skill. Also trigger when the user says 'create a skill', 'make a skill', 'improve this skill', 'update skill', 'turn this into a skill', or when a task is important and likely to repeat.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like 'the xlsx in my downloads') — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
| name | browser-use |
| description | Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Browser Use CLI 3.0 Python heredoc workflow. |
Direct browser control via CDP. For task-specific edits, use agent-workspace/agent_helpers.py. For setup, install, or connection problems, read https://github.com/browser-use/browser-harness/blob/main/install.md.
Domain skills are off by default. Set BH_DOMAIN_SKILLS=1 to enable them; see the bottom section.
If BH_DOMAIN_SKILLS=1 and the task is site-specific, read every file in the matching $BH_AGENT_WORKSPACE/domain-skills/<site>/ directory before inventing an approach.
browser-use command via terminal_run using a heredoc:
browser-use <<'PY'
new_tab("https://example.com")
print(page_info())
PY
import them.BU_CDP_URL); no chrome://inspect setup needed. On macOS it attaches to the running Chrome CDP endpoint - run browser-use --doctor if it can't connect.xvfb_gui only for non-browser Linux GUI apps in Docker (skills_read xvfb). Web browsing stays on browser-use.browser-use <<'PY'
print(page_info())
PY
browser-use. Use heredocs for multi-line commands.run.py calls ensure_daemon() before exec.new_tab(url), not goto_url(url).If the daemon cannot connect, run diagnostics:
browser-use --doctor
If Chrome remote debugging is not enabled, the harness opens:
chrome://inspect/#remote-debugging
Ask the user to tick "Allow remote debugging for this browser instance" and click Allow if Chrome shows a permission popup. Then retry the same browser-use command.
Use Browser Use cloud for headless servers, parallel sub-agents, or isolated work.
Authenticate once:
browser-use auth login
Or import a key safely:
printf '%s' "$BROWSER_USE_API_KEY" | browser-use auth login --api-key-stdin
Pick a short made-up name; r7k2 below is just a placeholder:
browser-use <<'PY'
start_remote_daemon("r7k2")
PY
BU_NAME=r7k2 browser-use <<'PY'
new_tab("https://example.com")
print(page_info())
PY
When the task is done and a cloud browser is still running, ask directly: "Should I close this browser now?" If yes, run stop_remote_daemon(name). Remote daemons bill until they stop or time out.
Do not start a remote daemon and then keep using the default daemon. Use the same name for BU_NAME.
Cloud profile cookie sync reference: https://github.com/browser-use/browser-harness/blob/main/interaction-skills/profile-sync.md.
capture_screenshot() to understand visible state.click_at_xy(x, y) -> screenshot again.wait_for_load().ensure_real_tab().js(...) for DOM inspection or extraction when coordinates are the wrong tool.cdp("Domain.method", ...).Never guess URLs. Search in the browser, then click the right result:
new_tab("https://html.duckduckgo.com/html/?q=<query>")
# screenshot → read result coordinates → click_at_xy(x, y) on the right link
If you get stuck on a browser mechanic, check https://github.com/browser-use/browser-harness/tree/main/interaction-skills.
BU_NAME, BU_CDP_URL, BU_CDP_WS, or start_remote_daemon(...).$BH_AGENT_WORKSPACE/agent_helpers.py.chrome://inspect/#remote-debugging must be enabled for local Chrome control.BU_CDP_URL is an HTTP DevTools endpoint; the daemon resolves it to WebSocket.stop_remote_daemon(name) or PATCH /browsers/{id} {"action":"stop"}.Only applies when BH_DOMAIN_SKILLS=1. Otherwise ignore domain skills.
When enabled, search $BH_AGENT_WORKSPACE/domain-skills/<host>/ before inventing an approach. goto_url(...) returns up to 10 skill filenames for the navigated host.