showme

name	showme
description	Open a real (headed) browser, drive it to a specific state in a web app — a feature, a flow, a particular screen, or a bug — then leave the window open for the user to click around in, with a short note on what to try and what to watch for. Use when the user wants to "show me X", "take me to that state/screen", "let me click around in it", "open a browser I can play with", "set up the repro", "drive me to <feature/flow/situation>", or describes any app state they want to experience firsthand.
allowed-tools	Bash(agent-browser:*)
disable-model-invocation	true

showme

Drive a headed browser to a described state, then hand the user the live window. The state can be anything — a feature to try, a flow mid-way, a specific screen, an edge case, or a bug. Your job is the tedious setup; theirs is the experiencing.

Depends on the agent-browser skill and the agent-browser CLI. This skill only adds the headed + leave-open + handoff wrapper — for the actual driving (navigate, snapshot, click, fill, login), load agent-browser and follow it; don't re-derive it here. If agent-browser isn't available, stop and say so rather than falling back to another automation tool.

Steps

1. Target — from context, work out the URL (prod/staging/localhost:PORT; start the dev server first if it's this repo's app and it isn't running), the preconditions that define the state, and the point of interest. Ask one tight question only if genuinely ambiguous.

2. Open headed, named session:

   agent-browser open --headed --session showme <url>
   

   No window? A headless daemon was already up — agent-browser close --all, then reopen.

3. Drive to the state via the agent-browser snapshot-and-ref loop, up to the point of interest.

4. Verify it yourself first — then decide whether to hand over. When the state is a claim to confirm (a bug, regression, or "X happens when you do Y"), and the key action is non-destructive, fire it yourself and check the outcome before involving the user. Don't hand over a window that "should" show something you haven't confirmed it shows.

   • It reproduced → reset to just-before the action (reload / undo) so the user can trigger it themselves, then hand over (step 5). Note that you confirmed it.
   • It did NOT reproduce (false positive) → stop. Don't hand over. Tell the user the claim didn't hold, with the evidence (what you did, what actually happened vs. expected). This is the whole point of trying first: catch false positives without making the user click through a dead end.
   • Action is destructive, or the state is open-ended exploration (not a specific claim) → don't fire it; leave it for the user and go to step 5.

5. Hand over — do NOT close. Leave the window open (the daemon keeps it alive) and tell the user, in a few lines:

   • It's open — session showme, on which page.
   • You are here — current state + what you set up (and that you confirmed the action works, if you did).
   • Try this — the exact action (e.g. "click the blue Save button").
   • You'll see — what should happen, so they know what to look for.

   Offer agent-browser close --session showme for when they're done.

Notes

• Reuse login state with --profile Default, or --profile ~/.showme-profile for a persistent custom profile.
• Never auto-close — the open window is the deliverable.