create-formal-verification-skill SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

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

mdr add painhardcore/pstack/create-formal-verification-skill@git:20261101.1922dfd

Pins git:20261101.1922dfd in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

painhardcore/pstack

Path

skills/create-formal-verification-skill/SKILL.md

Versions recorded

1

Latest version

git:20261101.1922dfd, committed Nov 1, 2026

Size

5,720 bytes

Repository stars

16

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

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 painhardcore/pstack/create-formal-verification-skill@sha256:3f32709bb5dc920a

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

Versions

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

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_tjazwfcu7ggksusz
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/create-formal-verification-skill
GET https://markdownregistry.com/api/v1/blob/3f32709bb5dc920a0f5380c4855f96e055571c5df232d1df9528e89171795c4f

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

Every file in painhardcore/pstack

Other files named create-formal-verification-skill

Browse by kind, by grade A, or by owner.