# Create Verification Skill

Generate a project-local verification skill that drives your app the way a user does, ...

- Repository: https://github.com/michael-denyer/pstack-claude (3725 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add michael-denyer/pstack-claude --skill create-verification-skill -g -a claude-code -y`
Codex: `npx skills add michael-denyer/pstack-claude --skill create-verification-skill -g -a codex -y`
Cursor: `npx skills add michael-denyer/pstack-claude --skill create-verification-skill -g -a cursor -y`
Gemini CLI: `npx skills add michael-denyer/pstack-claude --skill create-verification-skill -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add michael-denyer/pstack-claude`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Create a verification skill

On Codex, read the [platform mapping](../poteto-mode/references/codex-tools.md), including its per-skill notes, before following this skill.

On GitHub Copilot, read the [platform mapping](../poteto-mode/references/copilot-tools.md), including its per-skill notes, before following this skill.

On Muse, read the [platform mapping](../poteto-mode/references/muse-tools.md), 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](https://code.claude.com/docs/en/skills#run-and-verify-your-app)). 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:

The rest: https://github.com/michael-denyer/pstack-claude/blob/HEAD/plugins/pstack/skills/create-verification-skill/SKILL.md