create-formal-verification-skill SKILL.md skillA
create-formal-verification-skill from creedants/pstack-t3 is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add creedants/pstack-t3/create-formal-verification-skill@git:20261019.9dcf1d4Pins git:20261019.9dcf1d4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- creedants/pstack-t3
- Path
skills/create-formal-verification-skill/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261019.9dcf1d4, committed Oct 19, 2026
- First version recorded
- Oct 18, 2026
- Size
- 5,291 bytes
- Repository stars
- 15
- License
- MIT
Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, "model-check this race", "prove this invariant", or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.
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 formal 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. A test checks the cases that someone thought to write. Formal verification checks every case in a stated scope: every order of steps in a model, every input up to a bound, or every input. This skill finds the part of the repo where that matters most, verifies one property of it, and leaves a project-local skill that lets the next agent check a change against that property. Write that skill for an agent who reads it cold, mid-change, and has never seen your work. The user must be able to trust the result and act on it without learning the verification language. ## Choose the target from the code Answer from the codebase, and ask the user only what you cannot observe. If the user named an area or a bug, start there. A good target is a promise the code makes, where a break harms users and tests rarely reach the case that breaks it. Choose the strongest such target in the repo, not the one that is easiest to verify. ## Let the question choose the tool …
Read the whole file at its exact version.
How to install
mdr add creedants/pstack-t3/create-formal-verification-skill@sha256:b2d21c73489a53d1The line at the top of this page pins the label git:20261019.9dcf1d4, 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_paoexup2mysedged)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 18, 2026 and Oct 19, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.9dcf1d4 latest | 2026-10-19 | 9dcf1d4 | 5,291 B | A | view · diff |
| git:20261019.3339aa9 | 2026-10-19 | 3339aa9 | 4,810 B | A | view · diff |
| git:20261018.dec2d4b | 2026-10-18 | dec2d4b | 4,720 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 (5291 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
creedants/pstack-t3 · 15 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_paoexup2mysedged GET https://markdownregistry.com/api/v1/resolve?ref=creedants/pstack-t3/create-formal-verification-skill GET https://markdownregistry.com/api/v1/blob/b2d21c73489a53d1e4652a2bce04be27ebc5dd727d757215b8263e3feb269889
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 creedants/pstack-t3
Every file in creedants/pstack-t3