readmenator-receipts SKILL.md skillA
readmenator-receipts from grisuno/lazyown is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add grisuno/lazyown/readmenator-receipts@git:20261022.f2f4471Pins git:20261022.f2f4471 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- grisuno/lazyown
- Path
.claude/skills/readmenator-receipts/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261022.f2f4471, committed Oct 22, 2026
- Size
- 3,315 bytes
- Repository stars
- 300
- License
- AGPL-3.0
Ingest deploynator release receipts into the repository knowledge base and turn observed release evidence into graph edges, RELEASES.md and predictions. Use whenever the user mentions release receipts, "what did the last release actually do", deploynator --receipt/--trace output, release evidence, or asks to reconcile observed versus candidate versus predicted edges.
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
# ReadMenator: release receipts as evidence, not prose Deploynator can write a receipt JSON on every release (`deploynator release --receipt`, or `--dry-run --trace` for a feasible plan). `readmenator . receipts` reconciles those receipts against this repository's static symbol index and writes the release layer of the knowledge base. ## Golden rule `Fact = observed step (exit_code)`. `Candidate = feasible set from config/CLI/interface`. `Predicted = model, always labeled with version and provenance`. A prediction is never presented as fact. ## 1. Ingest ```bash readmenator . receipts [dir] # default dir: release-receipts/ ``` Reads every receipt JSON (oldest first, invalid files skipped, bounded history), maps captured commands to callers (`git` -> GitOperations, `gh`/`glab`/`bb` -> platform CLIs, stages like `release:<platform>` -> `Platform.create_release`), and writes: | Output | Content | |--------|---------| | `readmenator-releases/RELEASES.md` | One section per release: version, mode, status, platforms, key facts | …
Read the whole file at its exact version.
How to install
mdr add grisuno/lazyown/readmenator-receipts@sha256:f27d1d2d70ded939The line at the top of this page pins the label git:20261022.f2f4471, 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_pn3bazpqknjef2rh)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 22, 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 (3315 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
grisuno/lazyown · 300 stars · license AGPL-3.0 · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pn3bazpqknjef2rh GET https://markdownregistry.com/api/v1/resolve?ref=grisuno/lazyown/readmenator-receipts GET https://markdownregistry.com/api/v1/blob/f27d1d2d70ded9394dc17d361357b94fd51f5ae1e8d3aa3d115c64cb2b23caba
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.