Menu

Individual skill

create-verification-skill

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", or when a project has no scripted way to prove UI/CLI/service behavior.

skills/create-verification-skill/SKILL.md

Read pinned source

Source commit 91251ca92b107de606d3958e86454441910f1179

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
18
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Create a verification skill

Read [the pstack-t3 runtime](../pstack-runtime/SKILL.md) before spawning workers, choosing models, scheduling, or isolating work. It maps those steps onto T3's orchestrator tools.

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 tailored to the repo. T3 can run any provider, and providers load project skills from different directories, so the skill is written once to `.agents/skills/verify-<app>/` (read by Codex and Cursor) and linked at `.claude/skills/verify-<app>` (read by Claude Code). Every T3 provider then sees it in the `$` skill picker. 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:

- **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: T3's preview tools for web and Electron (`preview_open`, `preview_snapshot`, `preview_act`, `preview_wait_for`, `preview_evaluate`), a tmux/PTY harness for CLI/TUI, plain HTTP for services, and T3's `device_list`, `device_open`, `device_screenshot`, and `device_close` for mobile apps on simulators or devices. See the runtime's [Verification surfaces](../pstack-runtime/SKILL.md#verification-surfaces). Preview tools are first-class drivers, not a fallback. Prefer them over a hand-rolled CDP harness unless the repo already ships one or the run must happen outside T3 (CI, a headless script).
- **Observe:** what evidence can be captured? Screenshots, terminal transcripts, response bodies, logs, exit codes, DB state.