update SKILL.md skillA
update from amd-agi/hyperloom is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add amd-agi/hyperloom/update@git:20261111.eef3c68Pins git:20261111.eef3c68 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- amd-agi/hyperloom
- Path
src/hyperloom_arbor/.claude/skills/dossier/update/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261111.eef3c68, committed Nov 11, 2026
- Size
- 10,132 bytes
- Repository stars
- 272
- License
- a license file GitHub does not identify
Update the dossier in a round after a long campaign or a merge has moved the served tree: 03.uK the code read again, 06.uK the baseline, 07.uK the profile, 10.uK what the campaigns learned (every KEEP, kill and probe, and which kills are reopenable), 11.uK the directions again with a new map. Run by Arbor in the round_end chapter when a map is explored, or by the operator on a stopped campaign.
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
# Update: a dossier round on a tree that has moved **In a campaign, Arbor runs this skill in a turn of its own** when every direction of the map is closed. Its argument is the path of a brief: read the brief first. It names the dossier's directory and the campaign's program; the program's "MAP EXHAUSTED" or "FRESH START" section says which round this is and what it writes. **By the operator,** on a stopped campaign, follow "How" below. **The rules:** [the rules](../shared/rules.md), relative to this skill's directory. The files of a round are `NN.uK-<part>.md`, beside the originals ([the template](../shared/template.md)). **End your reply:** - with a `LEDGER:` FACT per file written; - when the round writes 11.uK, with its map as ONE `DIRECTIONS: [...]` line. As in part 11, no direction changes the weights' precision, and none set aside for it comes back (`dossier:directions`, "The map"). ## Updating the dossier: after a long campaign or a merge A dossier describes one tree. A campaign changes it one KEEP at a time, and a merge brings in other branches' work at once; after enough of either, the served code is laid out differently (a path split, a layer re-partitioned, a …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_sndwynb5mt4bbmb6/446bba42d2d8e5aefeefd4c09688249de1c49e3163182b14cba42344ad4df891.json
Then /plugin install update@markdownregistry-sndwynb5mt4bbmb6 in Claude Code. It installs git:20261111.eef3c68, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add amd-agi/hyperloom/update@sha256:446bba42d2d8e5aeThe line at the top of this page pins the label git:20261111.eef3c68, 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_sndwynb5mt4bbmb6)
1 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 amd-agi/hyperloom/update 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 update from somewhere else? Ask it: where did my update 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 1 version of this file, committed on Nov 11, 2026.
Watch this file (sign in, one email per new version)
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/update/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 (10132 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
amd-agi/hyperloom · 272 stars · license a license file GitHub does not identify · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sndwynb5mt4bbmb6 GET https://markdownregistry.com/api/v1/resolve?ref=amd-agi/hyperloom/update GET https://markdownregistry.com/api/v1/blob/446bba42d2d8e5aefeefd4c09688249de1c49e3163182b14cba42344ad4df891
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.
More from amd-agi/hyperloom
Every file in amd-agi/hyperloom