campaign-archive SKILL.md skillA
campaign-archive 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/campaign-archive@git:20261105.0d95dc2Pins git:20261105.0d95dc2 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/campaign-archive/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261105.0d95dc2, committed Nov 5, 2026
- Size
- 7,376 bytes
- Repository stars
- 262
- License
- a license file GitHub does not identify
Archive a running Arbor campaign to git and rebuild any campaign's exact source tree from the archive. Use when syncing campaign patches/ledgers to the Arbor repo, when asked to recover or reproduce a campaign's code, or when a landed.patch will not apply.
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
# Campaign archive and exact recovery An Arbor campaign's source tree lives **inside a Docker container** on a compute node (`/usr/local/lib/python3.12/dist-packages/vllm`, made into a git repo). It is not on NFS and not bind-mounted. It dies with the container. This skill covers getting the reproducible part into git, and rebuilding the tree byte-for-byte from what git holds. Verified: rebuild from the archive reproduces the live container tree, **every file identical by sha256**. ## Layout | Path | Contents | |---|---| | `<sessions root>/<campaign>/` | live session: `session.json`, `ledger.jsonl`, `landed.patch`, `stock_base/`, `iter_N/` | | `scripts/dsv41-campaign/` | `sync_campaign_to_git.sh`, `check_review_consistency.py`, the sbatch files | | `results/<workload>/runs/<campaign>/` | the archived slice | | `results/<workload>/CAMPAIGN_REVIEW.md` | hand-written analysis | Session folders run to gigabytes, but **nearly all of that is replayable aiperf telemetry**. Everything with intellectual content — patches, ledgers, verdicts, stock base — is a few megabytes. Archive that; leave `agentic_run/` behind. ## Sync ```bash bash scripts/dsv41-campaign/sync_campaign_to_git.sh …
Read the whole file at its exact version.
How to install
mdr add amd-agi/hyperloom/campaign-archive@sha256:8201311d6885c8d3The line at the top of this page pins the label git:20261105.0d95dc2, 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_jqwuv3p4ryfal2vw)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 5, 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 (7376 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 · 262 stars · license a license file GitHub does not identify · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jqwuv3p4ryfal2vw GET https://markdownregistry.com/api/v1/resolve?ref=amd-agi/hyperloom/campaign-archive GET https://markdownregistry.com/api/v1/blob/8201311d6885c8d32345fae260fdfef13775062c4d0568a99d912cd849eb4e86
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.