What problem does it solve? AI agents automating browsers often pick the wrong tool, leak sessions into throwaway profiles, fail logins silently, and leave orphaned browser processes running. This Skill establishes a cross-repo default policy so every browser task follows consistent rules for tool choice, profile usage, and cleanup. ## Core Features & Use Cases - Tool Selection Rules: Defaults to playwright-cli in headless mode, switching to Chrome with a dedicated automation profile only for authentication, SSO, 2FA, or bot-detection scenarios. - Session Hygiene: Enforces named persistent sessions, pre-flight checks for stray sessions via playwright-cli list, and verified cleanup at task end so no orphaned browsers remain. - Safety Boundaries: Prohibits account creation and password entry even on request, mandates hand-off of credential fields to the user, and requires explicit approval before touching the user's daily browser profile. - Use Case: An agent asked to log into a ticketing site and submit a form checks for stray sessions, launches the dedicated Chrome profile, verifies login state by reading page content, fills all non-credential fields, hands off the password step, and confirms zero browsers remain afterward. ## Quick Start Apply the browser automation policy to decide whether to use playwright-cli or Chrome for logging into this website, and clean up all sessions when finished.
