pre-release-verification skillA
pre-release-verification is agent-read markdown (skill) from yeaight7/agent-powerups: Use when a release candidate needs final checks before tagging, publishing, or production deployment..
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
## Purpose Block releases until the repository state, CI status, local validation, and publish metadata are known and reproducible. ## When to Use - Before creating a release tag. - Before deploying to production. - Before approving a release candidate prepared by another agent. - When CI is green but local package or catalog checks still need proof. Do not use as a substitute for fixing failures. If any gate fails, stop and report the blocker. ## Inputs - Intended version or deployment identifier - Current branch and commit - CI status for the release commit - Project-specific build, lint, test, and packaging commands ## Workflow 1. Confirm the working tree is clean: ```bash git status --short ``` 2. Confirm the release commit and recent history: ```bash git log --oneline --decorate -n 10 ``` 3. Confirm CI is green for the exact commit. For GitHub: ```bash gh run list --limit 5 gh run view <run-id> --json conclusion,status,headSha,url ``` 4. Run local validation. Use the project's documented commands, for example: ```bash npm run build npm test python scripts/validate-skills.py python scripts/validate-catalog.py ``` 5. Check for secrets or accidental local files: …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/pre-release-verification@git:20260606.3b3bb9dmdr add yeaight7/agent-powerups/pre-release-verification@sha256:3a4311fd442f2d70Pin 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_foxvojkij6jkymrf)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.3b3bb9d latest | 2026-06-06 | 3b3bb9d | 2,188 B | A | view · diff |
| git:20260502.052851b | 2026-05-02 | 052851b | 968 B | A | view · diff |
| git:20260502.b112af5 | 2026-05-02 | b112af5 | 145 B | B | view |
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 (2188 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
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_foxvojkij6jkymrf GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/pre-release-verification GET https://markdownregistry.com/api/v1/blob/3a4311fd442f2d7089851dca3b2ec2687db2a1c89d8130ad28fb59dbeca7cf95
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.