What problem does it solve? Projects often lack a scripted way to prove that the real app behaves correctly, leaving agents and developers to rely on manual clicking or unverified assumptions. This Skill interviews the repository and generates a tailored verification skill that launches the app, drives it the way a user would, and captures evidence. ## Core Features & Use Cases - Repo Interview: Detects the app's surface (web UI, CLI/TUI, API, desktop), run commands, drive harnesses (Playwright, CDP, tmux/PTY, HTTP), and observable evidence sources directly from the codebase. - Skill Generation: Writes .cursor/skills/verify-<app>/SKILL.md with launch, doctor, drive, evidence, cleanup, and helper sections grounded in real selectors and commands from the repo. - Feature Map Seeding: Creates a features directory with one file per user-facing feature describing how to reach it, drive it, and prove it works. - Self-Proof: Runs the generated skill end to end once before handover, confirming evidence survives cleanup. - Use Case: An agent working in a repo with no test harness invokes this Skill to produce a reusable verification skill that launches the dev server, drives a feature via Playwright, and saves screenshots as proof. ## Quick Start Ask the agent to create a verification skill for this repository so the app can be launched, driven like a user, and proven with captured evidence.