Create Verification Skill
Generate a project-local verification skill that drives your app the way a user does, ...
Install
npx skills add michael-denyer/pstack-claude --skill create-verification-skill -g -a claude-code -y- Repository
- michael-denyer/pstack-claude3.7k
- Category
- Design
- Updated
- 5d ago
- License
- MIT
- Context cost
- Mediumabout 1,752 tokens
- Runs scripts
- No, instructions only
What it does
Generate a project-local verification skill that drives your app the way a user does, any language, framework, or platform. Use for /create-verification-skill, \"make a control skill for this repo\", \"make a driver skill for this repo\", or when a project has no scripted way to prove UI/CLI/service behavior.
Create a verification skill
On Codex, read the platform mapping, including its per-skill notes, before following this skill.
On GitHub Copilot, read the platform mapping, including its per-skill notes, before following this skill.
On Muse, read the platform mapping, including its per-skill notes, before following this 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 (.claude/skills/verify/) tailored to the repo. Name it verify. At the repo root a project skill by that name replaces Claude Code's bundled /verify, which only the user can invoke, so every playbook that names the driver skill can call the project one (Claude Code 2.1.200 or later). In a monorepo, write it in the touched package directory instead. 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.
1. Interview the repo, not the user
Answer these from the codebase and only ask the user what you cannot observe:
