publish-health-check SKILL.md skillA
publish-health-check from okhp3/skillz is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add okhp3/skillz/publish-health-check@git:20260826.4e61aefPins git:20260826.4e61aef in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- okhp3/skillz
- Path
.agents/skills/publish-health-check/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260826.4e61aef, committed Aug 26, 2026
- First version recorded
- Aug 24, 2026
- Size
- 5,336 bytes
- Repository stars
- 3
- License
- MIT
Confirm the live Skillz Forge GitHub Pages site matches the last successful deploy run, independent of whether the last deploy-pages.yml run happened to report success.
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
# Publish health check Notices, without anyone manually querying the Actions API, when a Skillz Forge publish silently stops going live. ## Why this exists `.github/workflows/deploy-pages.yml` once failed on every push for months after a monorepo migration, and nobody noticed: pushes to `main` looked normal, but the live site quietly served a stale build. There was no signal that surfaced the failure without an agent deliberately going and checking. This check closes that gap two ways at once: 1. It re-checks the *last* `deploy-pages.yml` run's conclusion for `main`, so a failed publish is flagged even if nobody is watching the Actions tab. 2. It independently compares the *live* `catalog.json`'s `sourceCommit` against the commit that the last successful deploy run actually built (its `head_sha`) -- not against `main`'s current tip, since `deploy-pages.yml` only fires on a `push.paths` allowlist and plenty of legitimate `main` commits (docs, unrelated workflows) never trigger a deploy at all. A mismatch here means a run reported "success" but didn't actually ship the commit it built (a stale Pages cache, a mis-scoped …
Read the whole file at its exact version.
How to install
mdr add okhp3/skillz/publish-health-check@sha256:e750625fadad687eThe line at the top of this page pins the label git:20260826.4e61aef, 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_4fxa7jvj4isy2jsj)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 24, 2026 and Aug 26, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260826.4e61aef latest | 2026-08-26 | 4e61aef | 5,336 B | A | view · diff |
| git:20260826.fee2eb5 | 2026-08-26 | fee2eb5 | 5,041 B | A | view · diff |
| git:20260826.0a40f1f | 2026-08-26 | 0a40f1f | 4,685 B | A | view · diff |
| git:20260824.472ce03 | 2026-08-24 | 472ce03 | 4,268 B | A | view · diff |
| git:20260824.df57f0d | 2026-08-24 | df57f0d | 3,877 B | A | 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 (5336 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
okhp3/skillz · 3 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4fxa7jvj4isy2jsj GET https://markdownregistry.com/api/v1/resolve?ref=okhp3/skillz/publish-health-check GET https://markdownregistry.com/api/v1/blob/e750625fadad687ea254ca57baee67119c961b45cf42493e8bb86500fd34c1d4
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.