published-keyboard-recovery-check SKILL.md skillA
published-keyboard-recovery-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/published-keyboard-recovery-check@git:20260824.77a78a9Pins git:20260824.77a78a9 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/published-keyboard-recovery-check/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260824.77a78a9, committed Aug 24, 2026
- Size
- 2,072 bytes
- Repository stars
- 3
- License
- MIT
Confirm the published Skillz Forge review surface still preserves failed-contract keyboard recovery after a GitHub Pages deploy.
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
# Published keyboard recovery check
## Use when
Run after a Forge deploy (or on demand against the live site) to catch
hosting or artifact differences that local validation cannot see -- a stale
GitHub Pages artifact, a build that shipped without the failed-contract
recovery path, or the keyboard-recovery behavior itself regressing once
served from production.
## Callable command
```bash
node .agents/skills/published-keyboard-recovery-check/run.mjs
```
Set `FORGE_PUBLISHED_URL` to point at a non-default deployment (defaults to
`https://okhp3.github.io/skillz/`). In a post-deploy CI job, set
`EXPECTED_SOURCE_COMMIT` to the commit that was just deployed (e.g.
`${{ github.sha }}`) so a lagging Pages artifact is reported before the
keyboard checks even run.
## Inputs and outputs
The command drives a headless browser against the **published** site only --
plain, unauthenticated HTTPS requests, no repository access, no production
credentials. It forces a skill-detail contract load to fail and checks that
the failed-contract alert, the raw-markdown fallback link, and the focusable
panel remain keyboard reachable, exactly as validated locally by
…Read the whole file at its exact version.
How to install
mdr add okhp3/skillz/published-keyboard-recovery-check@sha256:ce83b55d3985b26fThe line at the top of this page pins the label git:20260824.77a78a9, 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_zw5grrmt2kv22v6n)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 24, 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 (2072 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_zw5grrmt2kv22v6n GET https://markdownregistry.com/api/v1/resolve?ref=okhp3/skillz/published-keyboard-recovery-check GET https://markdownregistry.com/api/v1/blob/ce83b55d3985b26fa9c79e33baf02670208280c87832790f0dbf12b570352965
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.