code-yeongyu/oh-my-openagent / packages/shared-skills/skills/browser
browser
VerifiedDrives a real browser through the omowright library from the js eval kernel: sites the user is already signed into, forms and clicks, JS-rendered pages, screenshots, web QA, extension popups, a human handoff for login, CAPTCHA or OTP, and a browser you own for scraping, bot-scored targets, network capture and QA traces. Use for any interactive browser task; not for a plain search or an unblocked static fetch.
| File | Kind | Size |
|---|---|---|
| .gitignore | other | 303 B |
| .npmignore | other | 160 B |
| ATTRIBUTION.md | markdown | 2.1 KB |
| SKILL.md | skill md | 10.3 KB |
| references/commands.md | markdown | 8.6 KB |
| references/install.md | markdown | 5.7 KB |
| references/owned-engine/README.md | markdown | 3.2 KB |
| references/owned-engine/frames-and-humans.md | markdown | 3.1 KB |
| references/owned-engine/ladder.md | markdown | 3.8 KB |
| references/owned-engine/network.md | markdown | 2.9 KB |
| references/recipes/1password.md | markdown | 2.8 KB |
| references/remote.md | markdown | 1.1 KB |
| scripts/browser-doctor-report.mjs | script | 5.5 KB |
| scripts/browser-doctor.mjsexecutable | script | 1.9 KB |
| scripts/browser-engine-guard.mjs | script | 3.5 KB |
| scripts/browser-install.mjsexecutable | script | 3.0 KB |
| scripts/omowright.mjs | script | 2.1 KB |
references/owned-engine/frames-and-humans.md
View on GitHub# Frames, overlays, dialogs, and the human
## Cross-origin frames and shadow DOM
A cross-origin iframe is a separate target with its own snapshot. `snapshotWithFrames(page)`
reconciles the child trees into the parent so one tree describes the whole page, and reports
`missingFrames` for any it could not enter; address child elements through the page-level ref
(`f1e3`) — never by fetching a frame handle first. Shadow roots are traversed by the snapshot
engine; they are not a special case for you.
## Overlays that swallow clicks
Two identical misses on an element that is clearly visible usually means something invisible sits
on top: a consent banner, a modal backdrop, a sticky header, a full-viewport tracking layer.
`describeLayers(page)` names the topmost fixed or sticky element covering the viewport, and
`snapshotWithLayers(page)` prefixes a snapshot with `@layers blocking=<role> "<name>"` when one
exists. Either the overlay is named — dismiss it and continue — or `@layers none`, which means the
miss has another cause and you climb the ladder instead.
## Dialogs never block
`alert`, `confirm`, `prompt`, and `beforeunload` are answered at the protocol layer, before the
page sees them: by a `dialog` listener that answers, otherwise by the `dialogPolicy` passed to
`connectPipe` (or `browser.setDialogPolicy`). Default to accepting (`{ accept: true }`; a policy
function receives a plain `{ type, message, defaultPrompt, url }` and returns `{ accept, promptText }`).
`page.on("dialog", (dialog) => ...)` hands each listener a Playwright-style `Dialog` object, not a
plain object: read it through methods (`dialog.type()`, `dialog.message()`, `dialog.defaultValue()`,
and the `dialog.url` getter). A listener can answer it itself, which replaces the policy for that
dialog; a listener that only observes leaves it to the policy:
```js
page.on("dialog", (dialog) => dialog.type() === "prompt" ? dialog.accept("42") : dialog.dismiss())
```
A dialog is answered once; a second `accept()` / `dismiss()` throws. A run that hangs on
an unhandled dialog looks exactly like a hang with no cause, which is the most expensive kind to
diagnose.
## Device emulation
`emulate(page, "iphone-14")` applies viewport, device scale factor, user agent and touch together;
changing only the viewport produces a desktop page at a phone size, which is not what you are
testing. `emulate(page, null)` restores. Re-read the viewport after emulating, and re-pin
coordinates.
## Handing the page to a human
When every rung fails on a login, a one-time code, or a challenge you cannot clear, the human is
the fallback, not the failure:
```js
const { outcome } = await omowright.requestHuman(page, {
prompt: "Please finish the sign-in in this window.",
until: { url: /\/dashboard/ }, // or { selector } or async (page) => boolean
timeoutMs: 300_000,
})
```
It brings the window to the front, shows a banner with a Done button, and waits on a
**condition** with a bounded timeout rather than a fixed delay. Respect the answer: `timed_out`
or `cancelled` is a stop, and the correct response is to report which rung failed with what
evidence. Working around the user's refusal is never correct.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |