use-my-browser

SKILL.md

Route browser-dependent work through the user's live session, not fresh automation.

Classifies tasks as static-capable (fetchable without interaction) or browser-required (needs rendered state, interaction, or live session), then routes accordingly

Covers logged-in dashboards, localhost apps, form uploads, DOM/iframe/Shadow DOM inspection, and anti-bot friction detection

Maintains domain-specific site-pattern notes to avoid repeating failed assumptions and to document stable routes, login quirks, and interaction primitives

Includes decision guides for iframe/lazy-load handling, media inspection, parallel page ownership, and recovery from stale selectors or navigation drift

Do not treat this skill as a generic browsing default. Route from the evidence you need, not from tool preference.

Every task must be classified before you choose a route:

static-capable: the evidence can be produced without live browser state, visible confirmation, or page interaction

browser-required: the evidence depends on rendered state, interaction, live session behavior, or browser-only structures

Only static-capable tasks may fall back to static retrieval, curl, or other non-browser paths. Once a task is browser-required, stay on the browser path and mark missing capability as blocked instead of silently downgrading.

Prerequisite check

This skill is for work inside the user's live browser session, not for launching a separate fresh automation browser.

Before doing browser automation, confirm that your environment already has access to a live browser stack that can provide the capabilities the task depends on, such as page inventory, task-owned page creation, page selection, snapshots or visible-state reads, DOM inspection, text or form input, uploads, dialogs, console inspection, and network inspection. The exact stack does not matter here: confirm capability, not brand.

If the live browser stack is unavailable, do not attempt browser automation through this skill. Only static-capable work may fall back to static retrieval.

Live browser automation can trigger anti-bot or anti-automation defenses on some sites. Use browser interaction only when the task truly needs it, and avoid unnecessary repetitive actions once the needed evidence has been obtained.