browser-operator
starsforks
How to install browser-operator?
rlaope/oh-my-hermes/browser-operator
$npx -y skills add rlaope/oh-my-hermes --skill browser-operator[omh] Hermes browser operator workflow: scope URL opening, page interaction, login/form boundaries, observations, and destructive confirmation gates.
SKILL.md
| 1 | # Browser Operator |
| 2 | |
| 3 | This is a Hermes-native `browser-operator` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `browser-operator` exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is already handled by a narrower explicit skill with stronger evidence. |
| 12 | - The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents. |
| 13 | - The only safe answer is to ask for missing authority, credentials, target, or observed evidence first. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: browser-operator open the staging checkout URL, click login, fill the form, and capture blockers. |
| 20 | - Expected behavior: Produce `prepare_browser_operator_card` with required context, wrapper actions, and not-evidence boundaries. |
| 21 | - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: browser-operator use saved credentials and submit the production payment form without confirmation. |
| 26 | - Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened. |
| 27 | - Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - The target URL, allowed interactions, prohibited interactions, auth boundary, and stop condition are explicit. |
| 32 | - Credentials, login, payment, purchase, destructive submission, scraping, and data export are gated or marked missing. |
| 33 | - Screenshots, DOM state, console/network logs, and click/form traces are reported only from observed browser evidence. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If no URL or target page is supplied, ask for the smallest target needed before opening a browser task. |
| 38 | - If login, payment, destructive mutation, or credential use is requested, require an explicit confirmation gate and do not proceed from vague intent. |
| 39 | - If the request is visual correctness rather than general page operation, route to visual-qa instead. |
| 40 | |
| 41 | ## OMH Context Rail |
| 42 | |
| 43 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 44 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 45 | - Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `agent-board`, `gateway-intent-card`, `voice-operator`, `+26 more`) - schedules, status, health, and ops review. |
| 46 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 47 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 48 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 49 | - Coverage: Every generated workflow skill carries this rail. |
| 50 | - Normal users talk to Hermes; OMH CLI is infra. |
| 51 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 52 | |
| 53 | ## Use When |
| 54 | |
| 55 | Use when Hermes should prepare or supervise a browser/page interaction request such as opening a URL, clicking, logging in, filling forms, or capturing page blockers without claiming browser execution. |
| 56 | |
| 57 | Strong routing signals: `browser-operator`, `browser operator`, `browser task`, `browser operation`, `browser automation`, `browser session`, `webpage operation`, `web page operation`, `open url`, `open the url`, `open page`, `open the page`, `visit url`, `visit page`, `navigate url`, `navigate page`, `click page`, `click this page`, `click button`, `click login`, `login page`, `fill form`, `fill the form`, `submit form`, `checkout url`, `capture blockers`, `page blockers`, `interactive page`, `browser trace`, `browser observation`, `playwright task`, `웹페이지`, `웹 페이지`, `브라우저`, `브라우저 작업`, `브라우저 조작`, `페이지 열고`, `url 열고`, `링크 열고`, `클릭`, `로그인`, `로그인 폼`, `폼 작성`, `폼 입력`, `캡처`, `막히는 부분` |
| 58 | |
| 59 | ## Catalog Metadata |
| 60 | |
| 61 | Category: `browser` |
| 62 | Phase: `browser-task` |
| 63 | Hermes role: `guide` |
| 64 | Quality tier: `workflow-surface-gated` |
| 65 | |
| 66 | Quality bar: |
| 67 | |
| 68 | - Name the user-facing workflow objective, required context, next action, and stop condition. |
| 69 | - Separate prepared guidance from obser |
People who liked this also viewed
6 picksType
- agent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web aSkillsJul 2026
- browser-act--- name: browser-act description: "Browser automation CLI for AI agents. NEVER run browser-act commands directly via Bash — always invoke this skill first. Use browser-act when a user mentions it bSkillsJul 2026
- playwright-cliAutomate browser interactions, test web pages and work with Playwright tests.SkillsJul 2026
- accessibilityAudit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make SkillsJun 2026
- anti-detect-browserLaunch and manage anti-detect browsers with unique real-device fingerprints for multi-account operations, web scraping, ad verification, and AI agent automation. Use when the user needs to run multiplSkillsMar 2026
- web-access所有联网操作必须通过此 skill 处理，包括：搜索、网页抓取、登录后操作、网络交互等。 触发场景：用户要求搜索信息、查看网页内容、访问需要登录的网站、操作网页界面、抓取社交媒体内容（小红书、微博、推特等）、读取动态渲染页面、以及任何需要真实浏览器环境的网络任务。SkillsMay 2026
