create-verification-skill
Create a verification skill
Every serious project needs a scripted way to drive the real app and prove behavior: launch it, exercise a feature the way a user would, and capture evidence. This skill generates that as a project-local skill (<skills-dir>/verify-<app>/) tailored to the repo. You write the generator's output for the next agent, not for a human: it will be read cold, mid-task, by an agent that has never seen the app.
0. Resolve <skills-dir>
The generated skill is harness-neutral, so resolve where it goes before writing anything. Use the first match:
- A project-local skills directory the repo already has:
.agents/skills/,.claude/skills/,.codex/skills/,.cursor/skills/, or.pi/skills/. When several exist, take the one holding the most skills. - Otherwise
.agents/skills/, the neutral default.
If a second harness's skills directory also exists, symlink the generated skill into it instead of copying, so the two cannot drift. On Windows, copy and say in the report that the copy will drift. Name the resolved path in your final report.
1. Interview the repo, not the user
Answer these from the codebase and only ask the user what you cannot observe: