galiprandi/job-seeker / .agents/skills/browser-automation
browser-automation
VerifiedControl 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.
sites/google_com/login-flow.md
View on GitHub---
name: google-login
description: Google account sign-in flow with phone-number confirmation and device-notification approval. Use when automating Google login via agent-browser in headed mode.
---
# Google Account Login Flow
Guide for completing Google sign-in when an existing browser session is not available. Validated against `accounts.google.com` Spanish UI.
## Prerequisite
Read the main Browser Automation `SKILL.md` for profile setup and the safe wrapper. This flow requires **headed mode** because it involves a human-in-the-loop device notification.
## Setup
```bash
node .agents/skills/browser-automation/scripts/browser.js open "https://accounts.google.com" --headed
```
## Flow
**Interaction doctrine (semantic-first):** use `find` semantic locators; `snapshot -i` @eN refs as fallback; `eval` only as last resort.
1. **Enter email.** Fill the textbox labeled `Correo electrónico o teléfono` (EN: `Email or phone`) and click **Siguiente** (EN: **Next**).
2. **Choose an alternative if asked for a password.** If the next screen asks for a password and the user wants to avoid typing it, click **Probar otra manera** (EN: **Try another way**).
3. **Confirm a phone number.** Google may ask the user to confirm a phone number it already knows. The number is displayed masked. This step requires the user to confirm that the number is still valid.
4. **Approve on the phone.** Google sends a notification to the user's linked Android / iOS device. The user must tap **Sí, soy yo** or equivalent.
5. **Login completes.** After approval, the browser redirects to `myaccount.google.com` (or the originally requested service).
## Locators (Spanish UI — semantic via `find`)
```bash
# Email input (textbox labeled "Correo electrónico o teléfono")
node .agents/skills/browser-automation/scripts/browser.js exec find label "Correo electrónico o teléfono" fill "user@example.com"
# Next button
node .agents/skills/browser-automation/scripts/browser.js exec find text "Siguiente" click
# Try another way
node .agents/skills/browser-automation/scripts/browser.js exec find text "Probar otra manera" click
```
Fallback CSS selectors (for `eval` or `snapshot -i` inspection only):
| Element | Selector |
|---|---|
| Email input | `input[aria-label="Correo electrónico o teléfono"]` |
| Next button | `button` containing text `Siguiente` |
| Try another way | `button` containing text `Probar otra manera` |
## Verification
After step 5, the page title should become `Cuenta de Google` and the URL should contain `myaccount.google.com`.
```bash
node .agents/skills/browser-automation/scripts/browser.js exec eval "(() => document.title.includes('Cuenta de Google'))()"
```
## Anti-patterns
- **Do not** attempt to type the user's password for them. This flow is designed for human-in-the-loop approval.
- **Do not** fill the masked phone number from memory; the user must confirm it.
- **Do not** reuse an old storage state without first checking whether the session is still valid, because Google may force re-verification.
## Notes
- The exact wording and available options depend on the user's 2FA configuration.
- If the device does not receive the notification, the user can request a fallback such as SMS.
- The email typed by the agent should be the one the user explicitly provided.
**Validated:** 2026-08-19 against live `accounts.google.com`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Unverified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |