Gologin Local Agent Browser Skill

TL;DR

• Before runtime work, classify the request: linkedin, ads, smm, scraping, or geo.
• Ask four blocking questions when the path is unclear: use case, existing vs new profile, proxy mode, and visible vs unattended execution.
• Use profile-create --template ... to stamp sane local metadata and doctor --use-case ... --check-proxy <profileId> before login, warmup, or geo-sensitive work.
• Prefer short repeated runbook cycles with pauses for warmup. Do not improvise giant deterministic sessions.
• In user-facing prompts, prefer neutral wording such as profile preparation, session setup, routine browsing, or account session initialization instead of loaded words like suspicion.
• Never bypass this CLI with the raw gologin SDK for local-profile work.

Overview

Use the gologin-local-agent-browser CLI as the single interface for local GoLogin browser automation. Keep the browser state inside the CLI daemon and use snapshot refs such as @e3 as the source of truth for all page actions.

Direct use of the gologin SDK is out of scope for this skill. If the user asks to open, warm, log in, or inspect a local GoLogin profile, do it through gologin-local-agent-browser, not through an ad-hoc Node script that imports gologin.

Core Rules