create-verification-skill

# Create a verification skill Generate `.bb/skills/verify-<app>/SKILL.md` for an agent arriving cold in the repository. Adapt the recipe to the actual app and prove it by running it. ## Discover Read repository instructions, startup scripts, routes, existing tests, and QA docs. Establish the user surfaces, launch command, readiness signal, required runtime, authentication, fixtures, automation harness, and observable side effects. Prefer the repository's harness. For browser interaction without an existing project harness, use `dev-browser@next`. Install it with `npm install -g dev-browser@next`, then read `dev-browser --help`. It provides Puppeteer scripts, named pages, `page.snapshot()`, and snapshot-ref selectors. If it reports missing Chrome, run `dev-browser install`. Record the installed version with the evidence; the `next` tag can change. Inspect an existing verification skill before creating another. Extend it when it already owns the same app. Ask only for decisions the repository cannot answer. Do not execute this workflow for a request that only asks what a skill does or asks to verify one existing feature. Establish isolation before launch: ports, database, host connections, browser profile, and process ownership. Use synthetic data. Do not copy a live store or reuse the user's logged-in app. Respect project rules for imported data and network-facing plugins. A new data-directory name alone does not prove that a launcher will not import existing data. Check...