Browser Pilot — browser-use scripts, planned & reviewed

Paste a browser-use automation script or describe the task in plain language, and get a browser-automation engineer's flight check: whether the job needs a browser at all (a plain fetch is often better), local Chrome or a managed cloud browser, a readiness posture (ready-to-run / needs-hardening / rethink-approach), prioritized findings with corrected Python across correctness, resilience, efficiency, auth-and-secrets, billing hygiene and etiquette, and the complete runnable heredoc script. A free instant prescan flags goto_url first navigations, missing wait_for_load, fixed sleeps, unverified clicks, raw AX-tree dumps, typed credentials, cloud daemons left billing or never named with BU_NAME, and recording slips before you spend anything. Derived from @browser-use/browser-use (MIT).

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.