create-verification-skill SKILL.md skillA
create-verification-skill from backnotprop/pstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add backnotprop/pstack/create-verification-skill@git:20261012.fce11a3Pins git:20261012.fce11a3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- backnotprop/pstack
- Path
skills/create-verification-skill/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261012.fce11a3, committed Oct 12, 2026
- First version recorded
- Aug 19, 2026
- Size
- 6,764 bytes
- Repository stars
- 3,337
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Create a verification 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 (`<skills>/verify-<app>/`) tailored to the repo. `<skills>` is your harness's project skill folder: `.cursor/skills/` in Cursor, `.claude/skills/` in Claude Code, `.pi/skills/` in Pi, `.agents/skills/` in Codex, OpenCode, and others. If the repo already keeps skills in one of these, use that one. 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. …
Read the whole file at its exact version.
How to install
mdr add backnotprop/pstack/create-verification-skill@sha256:bba612e8b81a02dfThe line at the top of this page pins the label git:20261012.fce11a3, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_nq3l6fquqvvcwkq2)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 19, 2026 and Oct 12, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.fce11a3 latest | 2026-10-12 | fce11a3 | 6,764 B | A | view · diff |
| git:20261012.f3afb70 | 2026-10-12 | f3afb70 | 6,533 B | A | view · diff |
| git:20260914.aa2db46 | 2026-09-14 | aa2db46 | 6,110 B | A | view · diff |
| git:20260819.4b32d9d | 2026-08-19 | 4b32d9d | 5,879 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6764 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
backnotprop/pstack · 3,337 stars · license MIT · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nq3l6fquqvvcwkq2 GET https://markdownregistry.com/api/v1/resolve?ref=backnotprop/pstack/create-verification-skill GET https://markdownregistry.com/api/v1/blob/bba612e8b81a02df0f49e6f6911f3b543c8c7d9f1f3c13ae6c0e2d58cc8c3ad3
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from backnotprop/pstack
Every file in backnotprop/pstack