create-verification-skill

Generates a project-local verification skill that drives an app like a user and captures evidence.

6.6k|542|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cursor/plugins --skill create-verification-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-verification-skill
Source: https://github.com/cursor/plugins/tree/main/pstack/skills/create-verification-skill
Command: npx skills add https://github.com/cursor/plugins --skill create-verification-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Projects often lack a scripted way to prove that real user-facing behavior works. This Skill interviews the repository, then generates a project-local verification skill (.cursor/skills/verify-<app>/) that launches the app, drives it the way a user would, and captures evidence.

Core Features & Use Cases

  • Repo Interview: Identifies the app's surface (web UI, CLI/TUI, API, desktop), launch command, driving harness (Playwright, CDP, tmux/PTY, HTTP), and observable evidence sources directly from the codebase.
  • Skill Generation: Writes a complete SKILL.md with Launch, Doctor, Drive, Evidence, Cleanup, and Helpers sections grounded in real selectors and commands from the repo.
  • Feature Map Seeding: Creates a features/ directory with one file per user-facing feature, following a strict four-section contract (Sub-features, user POV entry points, harness driving steps, Gotchas).
  • Self-Proof: Runs the generated skill end to end once — launch, doctor, drive one feature, capture evidence, clean up — before handing it over.
  • Use Case: A repo with a web app and CLI has no scripted verification. Run this Skill to produce a verify-<app> skill that any future agent can execute cold to prove features work.

Quick Start

Ask the agent to create a verification skill for this repository so the app can be launched, driven, and proven with captured evidence.

Frequently Asked Questions about create-verification-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a verification skill for my repository?

Invoke the create-verification-skill workflow, which interviews your codebase for its surface, launch command, and driving harness, then writes a project-local skill under .cursor/skills/verify-<app>/ with launch, doctor, drive, evidence, and cleanup instructions.

What kinds of apps can a generated verification skill drive?

It supports web UIs via browser or CDP harnesses, CLIs and TUIs via tmux or PTY sessions, and services via plain HTTP. The interview step picks existing harnesses like Playwright or Cypress specs first before falling back to generic recipes.

What is the feature map in a verification skill?

The feature map is a features/ directory with one Markdown file per user-facing feature. Each file lists sub-features, user entry points, exact driving commands with observable results, and gotchas, serving as the maintained source for verification runs.

Does the generated verification skill get tested before use?

Yes. The workflow requires running the generated skill end to end once: launch, doctor, drive one mapped feature, capture evidence, and clean up. A generated skill that was never executed is treated as a draft, not a deliverable.

How does cleanup work without killing the wrong processes?

Cleanup only tears down instances the verification run started, never killing by process name. Proof artifacts survive teardown in a named location, and cleanup runs after failed iterations too so broken attempts do not strand processes or ports.