pe-verify SKILL.md skillA
pe-verify from backnotprop/product-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add backnotprop/product-engineering/pe-verify@git:20260826.1e70df9Pins git:20260826.1e70df9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- backnotprop/product-engineering
- Path
skills/pe-verify/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260826.1e70df9, committed Aug 26, 2026
- First version recorded
- Aug 26, 2026
- Size
- 6,389 bytes
- Repository stars
- 25
- License
- Apache-2.0
Prove that behavior works, with evidence. Use after a feature is built ("verify this", "create a verification for the toolbar") or to re-run the project's QA list before a release ("run the QA list", "release check"). Classifies each check as code, browser, or mixed; drives the product with Playwright, recording video and checkpoint screenshots; writes one report.json and renders it into a branded HTML report with a checkpoint video player. Triggers on verify, verification, "does it work…
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
# Verify Proof that behavior works. This spine routes; the report contract, the QA-list conventions, and the capture method live in `references/` — load what the run needs. ## Contract (both modes) - **Read-only toward product code.** A failed check is reported, never fixed here; hand it to the pe-build skill by name. The only repo write this skill ever makes is the user's QA list, and only when the user asks to seed or edit it. - **Everything a run produces lands in a temp folder**: `pe-verify/<repo>/<YYYY-MM-DD-HHMM>/` under the system temp directory (`$TMPDIR`, else `/tmp`) — JSON, HTML, recordings, screenshots. Never inside the repo, never committed. Copy `report.json` into `.product/runs/` only on an explicit request. - **One JSON file is the deliverable.** Never write HTML. This skill's `scripts/render-report.py` turns `report.json` into `report.html` beside it; validate first, render, then open it (`--open`) and print the path. The contract is `references/report-schema.md`. - **Evidence or it is not a finding.** Every fail and flag carries a `file:line`, a recording timestamp, or the command that showed it. …
Read the whole file at its exact version.
How to install
mdr add backnotprop/product-engineering/pe-verify@sha256:18a7611a2dfa5a97The line at the top of this page pins the label git:20260826.1e70df9, 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_4vyivrk2minulc7c)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Aug 26, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260826.1e70df9 latest | 2026-08-26 | 1e70df9 | 6,389 B | A | view · diff |
| git:20260826.30b96c6 | 2026-08-26 | 30b96c6 | 5,603 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 (6389 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/product-engineering · 25 stars · license Apache-2.0 · pushed 2026-08-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4vyivrk2minulc7c GET https://markdownregistry.com/api/v1/resolve?ref=backnotprop/product-engineering/pe-verify GET https://markdownregistry.com/api/v1/blob/18a7611a2dfa5a977000eb4223cb3e917b98c8ead0b8b9dce9fe2baba26379aa
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.