study SKILL.md skillA
study 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/study@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/benchmark/study/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261111.eef3c68, committed Nov 11, 2026
- Size
- 6,067 bytes
- Repository stars
- 272
- License
- a license file GitHub does not identify
Study the benchmark a campaign is judged on, once, for every campaign on it: the rules a change could break (what it fixes, forbids and requires, each with its source and who checks it, as rules.yaml), its reference configuration and published number and how to measure it on the session's node, and what to measure (the official metric and units, the secondary metrics, the operating points, how many runs a claim needs). Writes benchmarks/<name>/. Run by Arbor in the benchmark chapter, before…
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
# Study the benchmark A campaign that does not know its benchmark keeps the wrong changes, and they are expensive. Each of these can cost a campaign its result: - **Under the benchmark's correct rules,** a tuned config can run slower than the reference. - **Natural speculative acceptance** can look like a free P90 gain, where the benchmark fixes golden acceptance. - **Scoring output throughput** while the chart plots P90 interactivity can adopt a change that lowers P90. This skill writes down, once per benchmark, what every campaign on it must respect and measure. The dossier's part 4 copies the rules in, and the gates check them. **In a campaign, Arbor runs this skill in a turn of its own,** before the dossier. Its argument is the path of a brief: read the brief first. It names the benchmark's directory (`benchmarks/<name>/`) and the files to write. **By hand,** the directory is `benchmarks/<benchmark>-<workload>/`, for example `benchmarks/inferencex-agentx/`. **Look first.** When the directory exists, read its `README.md`, then refresh only what is stale: a new revision of the …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_htzmjmzhbeac7s2f/1603754040080b012afa16e36759fa118c07099fd049509ab92e3c1c5928c5b7.json
Then /plugin install study@markdownregistry-htzmjmzhbeac7s2f 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/study@sha256:1603754040080b01The 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_htzmjmzhbeac7s2f)
2 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/study 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 study from somewhere else? Ask it: where did my study 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/study/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 (6067 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_htzmjmzhbeac7s2f GET https://markdownregistry.com/api/v1/resolve?ref=amd-agi/hyperloom/study GET https://markdownregistry.com/api/v1/blob/1603754040080b012afa16e36759fa118c07099fd049509ab92e3c1c5928c5b7
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