verify-landing-queue SKILL.md skillA
verify-landing-queue 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/verify-landing-queue@git:20261103.c236681Pins git:20261103.c236681 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- creedants/pstack-t3
- Path
.claude/skills/verify-landing-queue/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261103.c236681, committed Nov 3, 2026
- Size
- 9,936 bytes
- Repository stars
- 18
- License
- MIT
Check the landing queue and its path leases against the TLA+ model in verification/landing-queue/. Use when a change touches t3/added/landing/scripts/landing_lib/, before you trust a claim about lease overlap, queue order, one trunk writer, what merges, or recovery after a crash.
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 the landing queue `verification/landing-queue/LandingQueue.tla` and the sibling modules beside it are a hand-written TLA+ model of the landing queue and its path leases. TLC checks the model inside a stated bound. TLA+ checks the model. It does not read the Python. A rerun of an unchanged model passes after a real code regression, with the same state counts. A passing rerun alone does not show the model matches the current code. Before a passing run counts, and before `Verified at` moves, compare each affected action and its helper assumptions with the changed code and update the model to match. Start from the diff, not from the table. Run `git diff --stat <Verified at> ..HEAD -- t3/added/landing/scripts/landing_lib/` and read every changed function against its action before you run anything. A function can change behaviour without moving a transaction boundary and without appearing in the table's right column. Read every result with the pstack `/statechart` skill. It turns an invariant violation into the shortest path to it in plain words, and draws the state graph when nothing breaks. Use it rather than reading `tlc.out` yourself. …
Read the whole file at its exact version.
How to install
mdr add creedants/pstack-t3/verify-landing-queue@sha256:e16006dadf5f3628The line at the top of this page pins the label git:20261103.c236681, 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_ulgnwk2xhs3mkexy)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 3, 2026.
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 (9936 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 · 18 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ulgnwk2xhs3mkexy GET https://markdownregistry.com/api/v1/resolve?ref=creedants/pstack-t3/verify-landing-queue GET https://markdownregistry.com/api/v1/blob/e16006dadf5f3628bd08336ec40787a8c0533570779505418cf08d1f0cf9959d
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.