validate-a-release skillA
validate-a-release is agent-read markdown (skill) from different-ai/openwork: Validate the release, check the released binaries, is 0.18.x safe to roll out, prove a published desktop release. Boots the RELEASED mac-arm64 enterprise and cloud binaries through the packaged journeys, checks updater manifests and notarization, and publishes evidence..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Skill: validate-a-release
Run after `release` reports the GitHub release published. Every check runs on
the artifacts users download, never on a local build. macOS arm64 host, MySQL
on `127.0.0.1:3306` (`pnpm dev:den:mysql`), `gh` authenticated. Work from a
clean checkout (evidence is bound to its `git HEAD`): `origin/dev` today; from
the first release that ships these specs, the tag's own checkout
(`git worktree add /tmp/ow-vX.Y.Z vX.Y.Z`) so the gate matches the binary.
## 1. Download and unpack
`V` is the release under test, `B` the previous release existing users update from.
```bash
export V=0.18.45 B=0.18.42
export R=/tmp/ow-release-$V; mkdir -p $R && cd $R
gh release download v$V -R different-ai/openwork -p "openwork-enterprise-mac-arm64-$V.zip" -p "openwork-cloud-mac-arm64-$V.zip" -p '*.yml' --clobber
gh release download v$B -R different-ai/openwork -p "openwork-enterprise-mac-arm64-$B.zip" --clobber
for s in enterprise:$V cloud:$V enterprise:$B; do f=${s%%:*}; v=${s##*:}; rm -rf $f-$v; mkdir $f-$v
ditto -x -k openwork-$f-mac-arm64-$v.zip $f-$v && xattr -dr com.apple.quarantine $f-$v; done
…Read the whole file at its exact version.
How to install
mdr add different-ai/openwork/validate-a-release@git:20260910.741b90bmdr add different-ai/openwork/validate-a-release@sha256:e823397e43cfc35bPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ecpgnwhud2xv6nxf)
1 badge views in 30 days
Versions
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 (6844 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
different-ai/openwork · 23,724 stars · license NOASSERTION · pushed 2026-09-25 · branch dev
API
GET https://markdownregistry.com/api/v1/artifacts/art_ecpgnwhud2xv6nxf GET https://markdownregistry.com/api/v1/resolve?ref=different-ai/openwork/validate-a-release GET https://markdownregistry.com/api/v1/blob/e823397e43cfc35b257f290e763f9bd2bda48b0e8c857fdbf524146b1ce04aac
Your agent 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.