Skip to content

galiprandi/job-seeker / .agents/skills/browser-automation

browser-automation

Verified

Control a dedicated browser via agent-browser (Vercel). Use when automating web apps, scraping authenticated sites, filling forms, or navigating SPAs. Do NOT use for desktop apps or API-only integrations.

FileKindSize
SETUP.mdmarkdown3.0 KB
SKILL.mdskill md39.4 KB
references/agent-browser.mdmarkdown4.6 KB
references/api-capture.mdmarkdown1.8 KB
references/ats-patterns.mdmarkdown4.5 KB
references/audio-transcription.mdmarkdown2.4 KB
references/custom-combobox.mdmarkdown5.0 KB
references/efficiency-patterns.mdmarkdown2.6 KB
references/golden-rules.mdmarkdown5.7 KB
references/key-patterns.mdmarkdown4.4 KB
references/network-console.mdmarkdown1.2 KB
references/parallel-agents.mdmarkdown6.2 KB
references/profile-management.mdmarkdown6.3 KB
references/token-extraction.mdmarkdown2.8 KB
scripts/README.mdmarkdown6.0 KB
scripts/agent-browser.template.jsonconfig333 B
scripts/browser-share.jsscript20.0 KB
scripts/browser.jsexecutablescript17.1 KB
scripts/teams.jsscript7.1 KB
scripts/test-find-guide.jsscript6.3 KB
scripts/transcribe-audio.jsscript3.6 KB
scripts/viewer.htmlother8.6 KB
sites/CONTRIBUTING.mdmarkdown11.0 KB
sites/LEARN.mdmarkdown5.4 KB
sites/afip_gob_ar/guide.mdmarkdown9.0 KB
sites/app_web3forms_com/guide.mdmarkdown7.1 KB
sites/buk_co/guide.mdmarkdown1.5 KB
sites/calendar_google_com/calendar-deeplink.mdmarkdown1.9 KB
sites/calendly_com/guide.mdmarkdown1001 B
sites/careers_epam_com/guide.mdmarkdown4.4 KB
sites/dash_cloudflare_com/guide.mdmarkdown7.7 KB
sites/discord_com/guide.mdmarkdown9.9 KB
sites/discord_com/login-flow.mdmarkdown3.2 KB
sites/docs_google_com/guide.mdmarkdown7.3 KB
sites/facebook_com/guide.mdmarkdown9.8 KB
sites/gmail_com/guide.mdmarkdown35.6 KB
sites/google_com/guide.mdmarkdown1.1 KB
sites/google_com/login-flow.mdmarkdown3.3 KB
sites/google_home_com/guide.mdmarkdown2.1 KB
sites/google_maps_com/guide.mdmarkdown8.4 KB
sites/groq_com/signup-apikey.mdmarkdown6.6 KB
sites/humand_co/guide.mdmarkdown6.9 KB
sites/jira_com/guide.mdmarkdown10.8 KB
sites/linkedin_com/guide.mdmarkdown27.4 KB
sites/linkedin_com/outreach-strategy.mdmarkdown1.2 KB
sites/linkedin_com/posting.mdmarkdown14.0 KB
sites/linkedin_com/voyager-api.mdmarkdown8.1 KB
sites/mercadolibre_com/guide.mdmarkdown4.5 KB
sites/onstrider_com/draftjs-editor-fill.mdmarkdown2.3 KB
sites/onstrider_com/guide.mdmarkdown11.3 KB
sites/onstrider_com/react-autocomplete-inputs.mdmarkdown4.0 KB
sites/outlook_office_com/calendar-deeplink.mdmarkdown2.2 KB
sites/outlook_office_com/guide.mdmarkdown14.0 KB
sites/property_directory/guide.mdmarkdown3.7 KB
sites/reddit_com/guide.mdmarkdown16.2 KB
sites/teams_com/guide.mdmarkdown10.3 KB
sites/teamtailor_com/guide.mdmarkdown6.5 KB
sites/vea_com_ar/guide.mdmarkdown8.8 KB
sites/whatsapp_com/guide.mdmarkdown21.3 KB
sites/whatsapp_com/login-flow.mdmarkdown3.0 KB
sites/whatsapp_com/message-extraction.mdmarkdown5.7 KB
sites/whatsapp_com/voice-notes.mdmarkdown7.1 KB
sites/workatastartup_com/guide.mdmarkdown1.5 KB

sites/LEARN.md

View on GitHub
# No site guide? Learn and contribute one.

This site is not documented in the skill yet. While automating it, act as a field researcher — learn what works, note what doesn't, and contribute a guide so future agents don't start from zero.

## What to discover

### Keyboard shortcut sequences (highest value)

Keyboard shortcuts are the most stable, token-efficient way to automate a site. Find them before anything else.

- Try `?`, `Shift+?`, `Ctrl+/` to open the shortcuts help panel (most apps have one)
- Try universal patterns: `Ctrl+K` (command palette), `/` (search), `Esc` (close), `Enter` (submit), `Tab` (next field), `Shift+Enter` (line break)
- Check the app's help/FAQ or search "keyboard shortcuts <app name>"
- Record every shortcut that works and what it does

**Most valuable: reproducible key sequences.** A single keypress is useful, but a *sequence* that deterministically achieves a goal is gold. Look for chained shortcuts that perform a complete action without any DOM interaction:

- `G then I` → go to inbox (Gmail)
- `C then type then Ctrl+Enter` → compose and send (Gmail)
- `Ctrl+K then type then Enter` → search and open (Discord, many apps)
- `N then type then Tab then type then Enter` → new item and fill form

When you find a sequence that works every time, record it as a **deterministic keypath**:

```
Sequence: G → I
Action: Go to inbox
Deterministic: yes (works every time, no DOM dependency)
```

These keypaths are what makes a guide valuable — they let future agents skip snapshots and clicks entirely.

### Workarounds and bad patterns (critical to document)

**What NOT to do is as important as what TO do.** If you hit a dead end, a broken approach, or a pattern that seems right but fails, document it so future agents don't waste time repeating your mistakes.

Record:
- **Selectors that look right but break:** "The Send button has class `.send-btn` but clicking it via `eval` doesn't trigger the send handler — the app listens on `mousedown` not `click`"
- **Shortcuts that don't work:** "`Ctrl+S` looks like save in the help panel but it triggers the browser save dialog, not the app's save"
- **APIs that return 403/401 unexpectedly:** "The `/api/messages` endpoint returns 401 even with valid cookies — it requires a CSRF token from the meta tag, not from cookies"
- **Navigation that breaks state:** "Using `goto` to navigate between sections loses the SPA state — must use in-app navigation instead"
- **Patterns that work once but not twice:** "The first `fill` on the search box works, but the second one doesn't clear the previous value — need `Ctrl+A` then `fill`"
- **Anti-bot detection triggers:** "Rapid keypresses trigger a captcha — need to add delays between shortcuts"

Format each as:

```
Bad pattern: <what seems like it should work>
Why it fails: <the actual reason>
Workaround: <what actually works>
```

### Stable selectors

CSS classes change with every deploy. Prefer these in order of stability:

1. `data-testid` attributes — most stable, often intentional
2. `aria-label` — stable, accessibility-driven
3. `role` attributes — stable, semantic
4. `id` — sometimes stable, sometimes generated
5. CSS classes — last resort, expect breakage

### Internal API endpoints

Many apps have internal APIs you can call directly from `eval` with the browser's cookies. To discover them:

- Use `exec requests` to list network requests after performing an action
- Use `exec request <index>` to inspect a specific request
- Look for JSON responses with data you need — calling the API directly is more reliable than scraping the DOM

### Login flows and gotchas

- How does login work? (QR code, email+password, SSO, 2FA)
- Are there captchas? (if so, note where they appear)
- Does the site detect headless mode? (if yes, note that headed mode is required)
- Are there rate limits or anti-bot measures?
- What breaks? What requires workarounds?

## How to record your findings

After your session, run:

```bash
node .agents/skills/browser-automation/scripts/browser.js contribute
```

This prints the learning template and instructions for creating a guide file.

**Target path:** `sites/<domain_slug>/guide.md` where `<domain_slug>` is the hostname with dots replaced by underscores (e.g., `example.com` → `example_com`).

## What a good guide looks like

A guide that future agents can use immediately has:

1. **Frontmatter with `verified` date** — `verified: YYYY-MM-DD` so agents know how fresh the guide is
2. **Keyboard shortcuts section at the top** — every shortcut and keypath sequence, formatted as a table or list
3. **Bad patterns section** — what doesn't work and why, with workarounds
4. **Stable selectors** — the ones that survive updates
5. **Internal API endpoints** — if discovered, with request/response shapes (scrubbed)
6. **Login flow** — how to get in, what to watch for
7. **Gotchas** — edge cases, rate limits, anti-bot measures

## Rules

- **Paraphrase, never transcribe.** Describe in your own words. Do NOT copy site DOM/errors verbatim.
- **Scrub sensitive data.** No tokens, cookies, auth headers, API keys, real URLs with IDs, emails, phone numbers, real names. Use placeholders.
- **Check for existing files** in `sites/<domain_slug>/` first — update if one exists, don't duplicate.
- **No scripts.** `sites/` is markdown-only. No `.js`, `.py`, `.sh`, `.ts` files.
- **Never publish without user confirmation.** Show the file to the user and ask before opening a PR.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall