cross-agent-repair-routing SKILL.md skillA
cross-agent-repair-routing 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/cross-agent-repair-routing@git:20261117.5d6cc46Pins git:20261117.5d6cc46 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wxxb789/hoa
- Path
skills/cross-agent-repair-routing/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261117.5d6cc46, committed Nov 17, 2026
- First version recorded
- Nov 15, 2026
- Size
- 9,611 bytes
- Repository stars
- 3
- License
- MIT
Get a defect repaired when it sits in another agent's write surface: establish the authority map, rule on the claim, reproduce under the reporter's environment, and escalate one scoped landing decision. Use when you found a bug you may not fix in a shared tree. Not for fixing your own files.
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
# Cross-agent repair routing You found a defect, you may not fix it (wrong write surface), and the tree is shared with other agents plus an automated publisher. This skill is the loop that gets it repaired without you overstepping or turning the thread into chatter. For the per-artifact detail behind each step, load `delegated-work-acceptance` (verify one sender's delivery) and `report-claim-audit` (audit a digest). For a defect that keeps coming back on one code path, `references/fixing-a-defect-class.md` turns the findings into an invariant the fixer must satisfy. Roles, not names: the **front door** classifies an incoming report and routes it; the **builder** owns the code path; the **domain owner** owns a subsystem's rules and review; the **operator** owns runtime/config landings, credentials, and session state. Your write surface is your own role contract; the defect belongs to whichever role owns the file, not to whoever noticed it. ## 1. Establish the authority map before touching anything - Read your own role contract and the fixer's: your write list, theirs, and what needs the operator. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xhawszaymd2ufkro/02d16b04fbfeb2f0a4c738c28311acd8ade669dd107049908912a60d1255be3b.json
Then /plugin install cross-agent-repair-routing@markdownregistry-xhawszaymd2ufkro in Claude Code. It installs git:20261117.5d6cc46, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add wxxb789/hoa/cross-agent-repair-routing@sha256:02d16b04fbfeb2f0The line at the top of this page pins the label git:20261117.5d6cc46, 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_xhawszaymd2ufkro)
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/cross-agent-repair-routing 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 cross-agent-repair-routing from somewhere else? Ask it: where did my cross-agent-repair-routing 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 17, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261117.5d6cc46 latest | 2026-11-17 | 5d6cc46 | 9,611 B | A | view · diff |
| v0.1.66 | 2026-11-17 | fd3bd52 | 9,615 B | A | view · diff |
| v0.1.65 | 2026-11-16 | e399a8d | 9,615 B | A | view · diff |
| v0.1.64 | 2026-11-15 | 0a361a6 | 9,615 B | A | view · diff |
| v0.1.63 | 2026-11-15 | 500714d | 9,615 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/cross-agent-repair-routing/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 (9611 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_xhawszaymd2ufkro GET https://markdownregistry.com/api/v1/resolve?ref=wxxb789/hoa/cross-agent-repair-routing GET https://markdownregistry.com/api/v1/blob/02d16b04fbfeb2f0a4c738c28311acd8ade669dd107049908912a60d1255be3b
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.