use-my-browserlisted

# Use My Browser This is the main browser automation strategy skill for nontrivial web work. It teaches the agent when to stay on public-web tools, when to use the live browser session, and when to fall back to a separate browser or raw-fetch path. Despite the name, it covers more than "use my current browser." It also teaches a broader browsing philosophy: define the goal first, choose the right network layer, treat results as evidence, prefer primary sources over recycled summaries, and keep live-session work minimally intrusive. ## When to Use Use this skill when any of these are true: - The user wants public-web research, source verification, or page inspection and the choice of tool matters. - The task depends on the user's current sign-in state or cookies. - The user already has the relevant page, element, or failing request open in Chrome DevTools. - The target is a social platform, anti-bot-heavy site, or other dynamic page where static fetches are likely to miss the real content. - The target page is dynamic, authenticated, or difficult to inspect with search and raw fetch alone. - The task needs the current DOM, console, network activity, performance data, file upload, or rendered media from the live browser session. - The user wants the agent to take over a debugging flow they already started manually in Chrome. Do not use this skill when: - The task is purely local and does not involve the web at all. - A separate clean browser context is safer than touchin