Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
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
# Maintain a verification skill
A feature map rots the moment the app changes. This skill is the upkeep loop for a skill generated by `/pstack:create-verification-skill` (or any project-local verification skill with a feature map). The unit of rigor is the feature, not every sentence: cover every feature file from source and exercise every feature live, without terminalising every bullet.
## Outcomes
Pick one, and say which:
- **clean** — every feature got source and live coverage; nothing worth shipping. No branch, no PR.
- **changed** — one PR ships proven doc, harness, or map corrections.
- **blocked** — coverage could not finish or a proven fix could not ship safely. Say exactly what blocked it.
## Edit scope
Only edit the verification skill's own directory (its SKILL.md, features/, and any harness scripts it owns). Never edit product code during a run: a behavior the map describes that the app no longer does is either doc drift (fix the map) or a product regression (report it, don't paper over it in docs).
## Pass
…
The line at the top of this page pins the label git:20260924.44c9277, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_q5r3f4sgybvsiepa
GET https://markdownregistry.com/api/v1/resolve?ref=lucasheriques/pstack/maintain-verification-skill
GET https://markdownregistry.com/api/v1/blob/d614d31a738820ed5f37b0104d9df3831b0ab0aabc9806b920a0899d34d8ce3d
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.
lucasheriques/pstack · .claude/skills/sync-upstream/SKILL.md · Merge the latest cursor/plugins pstack into this Claude Code port. Use for "sync upstream", "update pstack from…
lucasheriques/pstack · skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
lucasheriques/pstack · skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
lucasheriques/pstack · skills/automate-me/SKILL.md · Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a…
lucasheriques/pstack · skills/benchmark-checklist/SKILL.md · Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened)…
lucasheriques/pstack · skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
lucasheriques/pstack · skills/correct/SKILL.md · Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types…
lucasheriques/pstack · skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives your app the way a user does — any language, framework, or…
lucasheriques/pstack · skills/figure-it-out/SKILL.md · Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a…
lucasheriques/pstack · skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
paperclipai/paperclip · .agents/skills/maintain-verification-skill/SKILL.md · Keep a project's verification skill and product/agent access maps aligned with current source and real evidence. Use…
theonlyfusioncube/potetos-for-everyone · skills/maintain-verification-skill/SKILL.md · Repair a project verification skill whose feature map or commands drifted. Use when app behavior and verification docs…
