القائمة
Always use Browser Harness for web interaction that needs robust automation, downloads, uploads, screenshots, testing, or the user's live Chrome session.
التثبيت باستخدام 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 documents, .docx files, reports, memos, letters, templates, tables of contents, headings, page numbers, letterheads, tracked changes, comments, images, or document conversion.
Manage repositories, invitations, pull requests, and collaborator permissions.
Analyze videos, screen recordings, ads, and video links with LimeBot's native video tool. Use for requests to watch, summarize, transcribe, inspect a moment, read on-screen text, or answer questions about YouTube, Vimeo, TikTok, Loom, MP4, MOV, MKV, or WebM media.
Control a real, local web browser to search, navigate, and extract information.
Manage and interact with Discord servers, channels, and members.
An adaptive, stealthy web scraper that bypasses common anti-bot protections using Scrapling's StealthyFetcher, curl_cffi, and browserforge to extract raw text or CSS selectors.
| name | browser-harness |
| description | Always use Browser Harness for web interaction that needs robust automation, downloads, uploads, screenshots, testing, or the user's live Chrome session. |
| dependencies | {"python":[],"node":[],"binaries":["browser-harness"]} |
Browser Harness controls Chrome directly through CDP. The default upstream checkout is at:
$env:USERPROFILE\Developer\browser-harness
The installed CLI is the normal entry point. The checkout is available for its current
SKILL.md, install.md, interaction guides, and source diagnostics.
Pass Python helpers on standard input; -c and --setup are not valid commands:
@'
new_tab("https://example.com")
wait_for_load()
print(page_info())
'@ | browser-harness
Helpers are pre-imported. The daemon starts automatically on the first command.
Use new_tab(url) for the first navigation and call wait_for_load() afterward.
browser-harness --doctor
browser-harness --reload
browser-harness recordings
If local Chrome cannot attach, open chrome://inspect/#remote-debugging, ask the user
to enable Allow remote debugging for this browser instance, and wait for the user
to approve Chrome's popup. Do not claim Browser Harness is unavailable until
browser-harness --doctor or an actual harness command reports the failure.
Before inventing mechanics, read the relevant upstream guide under:
$env:USERPROFILE\Developer\browser-harness\interaction-skills\
Important guides include downloads.md, screenshots.md, uploads.md, tabs.md,
dialogs.md, and print-as-pdf.md.
For a site-specific flow, inspect the official examples under
$env:USERPROFILE\Developer\browser-harness\agent-workspace\domain-skills\.
Task-specific helpers belong in Browser Harness's configured agent workspace, not in
LimeBot core.
Recordings are disabled by default. Preserve the user's configured preference. Never enable background recordings without explicit consent.