browser-account-guardlisted
Install: claude install-skill praticoeq-sudo/browser-account-guard
# Right browser ≠ right account ≠ right target
Three real failures, all near-misses: a browser correctly identified as client A's opened
Search Console under client B's account (the browser's default) — one click from creating a
property in the wrong account. A correct login published to the wrong client's site. And
hours spent debugging a panel that "was logged out" and was simply the wrong account.
**One rule: never infer. Read it back — the account *and* the target — before you act.**
> **Reading a panel is not safe either.** Steps 0–6 and 8 apply to reads. The wrong property
> produces a confident, wrong report and drops one client's data into another client's
> transcript. Only step 7, the consent gate, is exempt for reads.
> **Unattended run (scheduled, headless, no human)? It is read-only.** The registry (step 8)
> answers step 1 — which account, which target. It does **not** answer step 3: knowing which
> browser you want is not the same as being placed in it. And it cannot answer step 7 —
> consent does not come out of a JSON file. If the job must create, publish, delete, send or
> pay, **stop, write the reason to the job's own log or output, and leave a draft**. Never
> treat "the schedule was approved once" as approval for tonight's action.
> **Terms of service.** Driving a logged-in UI with synthetic events may breach a platform's
> terms, and the suspension lands on *the client's* account. Prefer the API. When both work,
> the API is not merely sturdier — it