Adaptively prepare Tap for LOGGED-IN / authenticated websites — not by running a script blind, but by diagnosing first, fixing only the missing rung, passing the human trust gates, then verifying. Public pages / open APIs need none of this (the plugin's MCP over npx already works). Trigger when: the user wants to use Tap on a site that requires login (bank / admin dashboard / internal tool / social); the user says "set up tap", "configure tap", "connect tap", "tap won't connect", "let tap use my logged-in session"; or Tap's run fails on a logged-in site with a peer / bridge-unreachable error. This skill DRIVES setup adaptively via `tap embed --verify`; it does not blindly…
