create-verification-skilllisted

# Create a verification skill Create a project-local skill that another agent can read cold and use to prove the real application behavior. Do not write a generic test plan. Record the commands, stable handles, health checks, evidence, and cleanup that work in this repository. ## 1. Interview the repository Answer what you can from code and documentation before asking the user: - **Surface:** Identify the primary user surface and any secondary surfaces. - **Run:** Find the repository's own launch command, required environment, ports, seed data, and authentication. - **Drive:** Prefer an existing Playwright, Cypress, PTY, expect, API, desktop, or mobile harness. Otherwise use the host agent's available browser, terminal, desktop, or HTTP driver. - **Observe:** Identify screenshots, terminal transcripts, response bodies, logs, exit codes, files, and durable state that can prove behavior. - **Isolate:** Determine whether parallel instances can use distinct ports, profiles, or data directories. If not, require exclusive use. If the checkout does not run as documented, fix or precisely report that base problem before recording a workflow against it. ## 2. Choose the project skill root Use the current harness's project-level skill directory from [harness-paths.md](./references/harness-paths.md). Name the generated skill `verify-<app>` and create `<skill-root>/verify-<app>/SKILL.md`. The generated frontmatter must contain `name` and a precise `description`. Its bod