Home / shiwenbin1617 / pstack · GitHub

create-verification-skill SKILL.md skillA

create-verification-skill from shiwenbin1617/pstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add shiwenbin1617/pstack/create-verification-skill@git:20260827.f7b391a

Pins git:20260827.f7b391a in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: shiwenbin1617/pstack
Path: skills/create-verification-skill/SKILL.md
Versions recorded: 1
Latest version: git:20260827.f7b391a, committed Aug 27, 2026
Size: 5,935 bytes
Repository stars: 3
License: a license file GitHub does not identify

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 (`.claude/skills/verify-<app>/` (`.agents/skills/verify-<app>/` on Codex)) tailored to the repo. 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

The exact contents, by fingerprint

mdr add shiwenbin1617/pstack/create-verification-skill@sha256:001c8e1b867d7100

The line at the top of this page pins the label git:20260827.f7b391a, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_zgqzz3h7eygs2bdc.svg)](https://markdownregistry.com/a/art_zgqzz3h7eygs2bdc)

4 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Aug 27, 2026.

version	committed	commit	size	audit
git:20260827.f7b391a latest	2026-08-27	f7b391a	5,935 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (5935 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

GitHub

shiwenbin1617/pstack · 3 stars · license a license file GitHub does not identify · pushed 2026-09-07 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_zgqzz3h7eygs2bdc
GET https://markdownregistry.com/api/v1/resolve?ref=shiwenbin1617/pstack/create-verification-skill
GET https://markdownregistry.com/api/v1/blob/001c8e1b867d7100c6df2c46e451872089468ab484eff525a0fc6318d060ccea

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 shiwenbin1617/pstack

AGENTS.md AGENTS.md file

shiwenbin1617/pstack · AGENTS.md

git:20260907.b1269d9 · audit A · 3 stars

setup-pstack SKILL.md skill

shiwenbin1617/pstack · adapters/claude-code/overrides/setup-pstack/SKILL.md · Configure which Claude Code models pstack uses per role. Use for /setup-pstack or requests to change pstack model…