What problem does it solve? Automated browsers get blocked: ephemeral test browsers leak navigator.webdriver=true, lack cookies and logins, and trigger bot walls, CAPTCHAs, and 403s on JS-heavy or protected pages. This Skill attaches automation to the user's real, persistent, logged-in Chrome on a macOS host so sessions look and behave genuinely human. ## Core Features & Use Cases - Real-Chrome attachment: hb-connect.sh binds the agent-browser daemon to the host Chrome over CDP (port 9222) and asserts navigator.webdriver === false before any action. - Human-paced interaction verbs: the hb wrapper adds humantype, humanclick (curved, jittered mouse paths), think, fillform, waitfor, and consent-overlay dismissal via hb goto/hb dismiss. - Risk-scored wall handling: hb fpcheck, hb dd, hb warmup, and hb solve-wait detect DataDome/PerimeterX-style scoring and hand any rendered challenge to the human rather than auto-solving it. - Structured data extraction: hb data reads embedded __NEXT_DATA__/__NUXT__/JSON-LD blobs instead of scraping virtualized DOM lists. - Use Case: Sign up for a service that blocks headless browsers — open a mail.tm temp inbox with hb mail new, fill the signup form with human-paced typing, retrieve the verification code with hb mail code, and complete the flow from the genuine browser session. ## Quick Start Run the hb-connect.sh script to attach to my real Chrome, then use hb goto to open the bot-blocked page and read its content.