maintain-formal-verification-skill SKILL.md skillA

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

Install it, pinned
mdr add painhardcore/pstack/maintain-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/maintain-formal-verification-skill/SKILL.md
Versions recorded
1
Latest version
git:20261101.1922dfd, committed Nov 1, 2026
Size
6,981 bytes
Repository stars
22
License
MIT

Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, "is the model still true to the code", or after merges and refactors that touched verified code without rechecking it.

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 formal verification skill

A formal check proves a property of what it describes. When the code changes and the verification does not, the check can keep passing while it describes code that no longer exists. That pass is the dangerous case, because it looks like a proof. This skill is the upkeep loop for a verify skill that `/create-formal-verification-skill` generated, or for any project-local skill that runs a model checker, prover, or code-level verifier against named code. The project-local skill handles a change that an agent makes while it uses that skill. This skill handles the changes that skipped it: merges, edits made without the skill, and drift that builds up across many commits.

## Outcomes

Give each check one outcome, and say which:

- **in sync**: no change since the last sync alters what the check describes, and the check passes.
- **updated**: the code changed, the verification now describes the new code, and the check passes.
- **bug**: the verification describes the current code, and the code breaks the property. This is a finding about the code. It is not drift.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_mtpl3qq6ftuohbxi/72ada37e2478af4c3902ed7b2e858e930cbbf06625e0001cbdc8c5612965964f.json

Then /plugin install maintain-formal-verification-skill@markdownregistry-mtpl3qq6ftuohbxi in Claude Code. It installs git:20261101.1922dfd, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add painhardcore/pstack/maintain-formal-verification-skill@sha256:72ada37e2478af4c

The line at the top of this page pins the label git:20261101.1922dfd, 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 badge

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

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

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in painhardcore/pstack/maintain-formal-verification-skill since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of maintain-formal-verification-skill from somewhere else? Ask it: where did my maintain-formal-verification-skill come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

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

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261101.1922dfd latest2026-11-01 1922dfd 6,981 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

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 (6981 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

painhardcore/pstack · 22 stars · license MIT · pushed 2026-11-13 · branch master

API

GET https://markdownregistry.com/api/v1/artifacts/art_mtpl3qq6ftuohbxi
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/maintain-formal-verification-skill
GET https://markdownregistry.com/api/v1/blob/72ada37e2478af4c3902ed7b2e858e930cbbf06625e0001cbdc8c5612965964f

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

AGENTS.md AGENTS.md file
painhardcore/pstack · AGENTS.md
git:20261101.1922dfd · audit A · 22 stars
architect SKILL.md skill
painhardcore/pstack · skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
git:20261101.1922dfd · audit A · 22 stars
arena SKILL.md skill
painhardcore/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…
git:20261101.1922dfd · audit A · 22 stars
benchmark-checklist SKILL.md skill
painhardcore/pstack · skills/benchmark-checklist/SKILL.md · Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened)…
git:20261101.1922dfd · audit A · 22 stars
blast-radius SKILL.md skill
painhardcore/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…
git:20261101.1922dfd · audit A · 22 stars
bro SKILL.md skill
painhardcore/pstack · skills/bro/SKILL.md · Use when the user asks to restate or explain the last message in plain, jargon-free language.
git:20260827.04830a9 · audit A · 22 stars
correct SKILL.md skill
painhardcore/pstack · skills/correct/SKILL.md · Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types…
git:20261101.1922dfd · audit A · 22 stars
create-formal-verification-skill SKILL.md skill
painhardcore/pstack · skills/create-formal-verification-skill/SKILL.md · Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in…
git:20261101.1922dfd · audit A · 22 stars
create-verification-skill SKILL.md skill
painhardcore/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…
git:20261101.1922dfd · audit A · 22 stars
figure-it-out SKILL.md skill
painhardcore/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…
git:20261101.1922dfd · audit A · 22 stars
how SKILL.md skill
painhardcore/pstack · skills/how/SKILL.md · Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a…
git:20261101.1922dfd · audit A · 22 stars
in-your-own-words SKILL.md skill
painhardcore/pstack · skills/in-your-own-words/SKILL.md · Restate in your own words what you think the user's goals are and what problem they're trying to solve. Use for…
git:20261101.1922dfd · audit A · 22 stars

Every file in painhardcore/pstack

Other files named maintain-formal-verification-skill

maintain-formal-verification-skill SKILL.md skill
yeachan-heo/oh-my-claudecode · skills/maintain-formal-verification-skill/SKILL.md · Re-sync an existing formal verification skill after the covered code changed: re-check every assumption, update cited…
git:20261108.ac1df7f · audit A · 40,827 stars
maintain-formal-verification-skill SKILL.md skill
cursor/plugins · pstack/skills/maintain-formal-verification-skill/SKILL.md · Bring a project's formal verification back in line with the code after the code changes: find the commits that touched…
git:20261019.7b353f7 · audit A · 16,411 stars
maintain-formal-verification-skill SKILL.md skill
cursor/plugins · harness/pstack/claude-code/skills/maintain-formal-verification-skill/SKILL.md · Bring a project's formal verification back in line with the code after the code changes: find the commits that touched…
git:20261019.7b353f7 · audit A · 16,411 stars
maintain-formal-verification-skill SKILL.md skill
michael-denyer/pstack-claude · plugins/pstack/skills/maintain-formal-verification-skill/SKILL.md · Bring a project's formal verification back in line with the code after the code changes: find the commits that touched…
git:20261104.e66f85f · audit A · 4,340 stars
maintain-formal-verification-skill SKILL.md skill
backnotprop/pstack · skills/maintain-formal-verification-skill/SKILL.md · Bring a project's formal verification back in line with the code after the code changes: find the commits that touched…
git:20261019.6ddf66a · audit A · 4,184 stars
maintain-formal-verification-skill SKILL.md skill
theonlyfusioncube/potetos-for-everyone · skills/maintain-formal-verification-skill/SKILL.md · Bring a project's formal verification back in line with the code after the code changes: find the commits that touched…
git:20261023.9aa1985 · audit A · 22 stars
maintain-formal-verification-skill SKILL.md skill
creedants/pstack-t3 · skills/maintain-formal-verification-skill/SKILL.md · Bring a project's formal verification back in line with the code after the code changes: find the commits that touched…
git:20261019.9dcf1d4 · audit A · 19 stars
maintain-formal-verification-skill SKILL.md skill
arjitj2/open-pstack · plugins/pstack/skills/maintain-formal-verification-skill/SKILL.md · Bring a project's formal verification back in line with the code after the code changes: find the commits that touched…
git:20261027.9086657 · audit A · 16 stars

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