generated-runtime-repairs SKILL.md skillA
generated-runtime-repairs from wxxb789/hoa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wxxb789/hoa/generated-runtime-repairs@git:20261118.7b3f760Pins git:20261118.7b3f760 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wxxb789/hoa
- Path
skills/generated-runtime-repairs/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261118.7b3f760, committed Nov 18, 2026
- First version recorded
- Nov 15, 2026
- Size
- 7,750 bytes
- Repository stars
- 3
- License
- MIT
Repair repository-owned wrappers and scheduled routines without confusing source correctness with deployment. Use when a generated file misbehaves and the fix belongs in its template or generator, or when a reviewed patch must be landed and then materialized into a live runtime. Not for editing generated output by hand.
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
# Generated runtime repairs Repair repository-owned wrappers and scheduled routines without confusing source correctness with deployment. Load the repository contract and the relevant runtime skill for its supported commands. ## When to Use - A repo owns a template/routine that is materialized into agent profiles, cron jobs, or wrapper scripts. - A generated file misbehaves and the fix must go to the template/generator, not the generated copy. - A reviewed candidate patch must be landed into a shared checkout and/or deployed to the live runtime. ## 1. Freeze scope and current inputs - Verify relayed permission changes against the operator's primary record and current contract. Classify source edits, Git publication, and live runtime writes separately; standing commit/push authorization does not authorize profile/config/cron/session writes. - Fetch and fast-forward before source work. Inspect current status/diff and patch applicability immediately before landing; peers and scheduled publishers can invalidate an earlier clean-tree report. When landing a candidate built against an earlier base, prove each target file …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jh3ninvtvmf3jytc/f38094a1d3553bed6565c0db9ef378c3dedbf62eaab6743ba62f91331a6468c4.json
Then /plugin install generated-runtime-repairs@markdownregistry-jh3ninvtvmf3jytc in Claude Code. It installs git:20261118.7b3f760, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add wxxb789/hoa/generated-runtime-repairs@sha256:f38094a1d3553bedThe line at the top of this page pins the label git:20261118.7b3f760, 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_jh3ninvtvmf3jytc)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in wxxb789/hoa/generated-runtime-repairs since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of generated-runtime-repairs from somewhere else? Ask it: where did my generated-runtime-repairs come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Nov 15, 2026 and Nov 18, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261118.7b3f760 latest | 2026-11-18 | 7b3f760 | 7,750 B | A | view · diff |
| git:20261117.5d6cc46 | 2026-11-17 | 5d6cc46 | 7,750 B | A | view · diff |
| v0.1.66 | 2026-11-17 | fd3bd52 | 7,754 B | A | view · diff |
| v0.1.65 | 2026-11-16 | e399a8d | 7,754 B | A | view · diff |
| v0.1.64 | 2026-11-15 | 0a361a6 | 7,754 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/generated-runtime-repairs/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (7750 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
wxxb789/hoa · 3 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jh3ninvtvmf3jytc GET https://markdownregistry.com/api/v1/resolve?ref=wxxb789/hoa/generated-runtime-repairs GET https://markdownregistry.com/api/v1/blob/f38094a1d3553bed6565c0db9ef378c3dedbf62eaab6743ba62f91331a6468c4
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.