create-verification-skill

Topics in the source

• Create a verification skill
• 1. Interview the repo, not the user
• 2. Generate the skill
• 3. Seed the feature map
• 4. Prove the generated skill before handing it over
• 5. Offer the maintenance loop

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 (.agents/skills/verify- /) 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. Answer these from the codebase and only ask the user what you cannot observe: Surface: what does a user actually touch? A web UI, a CLI/TUI, a desktop app, an API, a mobile app, a library? A repo can have several; pick the primary one and note the rest. Run: how does the app start locally? Prefer the repo's own documented dev command (package scripts, Makefile, README quickstart). Note ports, env vars, seed data, auth. Drive: how can an agent interact with it programmatically? Existing harnesses first — Playwright/Cypress specs, expect scripts, PTY helpers, curl-able endpoints, a debug port. Only then pick a generic recipe: browser/CDP for web and Electron, a tmux/PTY harness for CLI/TUI, plain HTTP for services. Observe: what evidence can be captured? Screenshots, terminal transcripts,

This is an excerpt. Refer to the complete source and its current requirements.