remote-gpu-setup SKILL.md skillB
remote-gpu-setup from amd-agi/aklr is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add amd-agi/aklr/remote-gpu-setup@git:20261105.1156d71Pins git:20261105.1156d71 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- amd-agi/aklr
- Path
harness/skills/remote-gpu-setup/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261105.1156d71, committed Nov 5, 2026
- Size
- 2,606 bytes
- Repository stars
- 15
- License
- MIT
Add, re-probe, update or remove the clusters remote-gpu allocates on (~/.remote-gpu/clusters/), and verify them. Use for /remote-gpu-setup, when remote-gpu has no cluster or none that fits the task, or when the user asks to add, check or remove a cluster.
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
# remote-gpu-setup — configure remote-gpu's clusters
Each cluster is `~/.remote-gpu/clusters/<name>/`: a manifest `cluster.env` and an adapter
`cluster.sh`. How to write and check one is in `references/add-cluster.md`; read it before step 3.
```bash
RG=${CLAUDE_SKILL_DIR}/../remote-gpu/scripts/remote-gpu
```
Where `${CLAUDE_SKILL_DIR}` is not expanded, the scripts are in `harness/skills/remote-gpu/scripts/`
from the AKLR root.
`$ARGUMENTS`: `add|update|remove [NAME]` skips step 2; empty runs every step.
## 1. Show the clusters
```bash
grep -H -E '^(VERIFIED|DESCRIPTION|HOST|GPU_ARCH|GPUS_PER_NODE|ACCOUNTS|MAX_TIME)=' ~/.remote-gpu/clusters/*/cluster.env
ls ~/.remote-gpu/clusters/*/
```
One row per cluster: name, description, login, arch, accounts, `VERIFIED`. Mark it stale if
`VERIFIED` is over 90 days old or either file is missing. No clusters: go to step 3 with `add`.
## 2. Choose
One AskUserQuestion: add, update one (stale first), remove one, or done.
## 3. Act
- **add**: `add-cluster.md` steps 1–4. A name already listed is an `update`.
- **update**: copy the directory to `~/.remote-gpu/clusters/.<name>.bak/`, run `probe-cluster` on
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lhuhjy4bioewy4if/0b19ccfbfbc9756bb4c76648931c1238e2d9e1e9a508c614bf48f7420378cdcf.json
Then /plugin install remote-gpu-setup@markdownregistry-lhuhjy4bioewy4if in Claude Code. It installs git:20261105.1156d71, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add amd-agi/aklr/remote-gpu-setup@sha256:0b19ccfbfbc9756bThe line at the top of this page pins the label git:20261105.1156d71, 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_lhuhjy4bioewy4if)
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/aklr/remote-gpu-setup 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 remote-gpu-setup from somewhere else? Ask it: where did my remote-gpu-setup 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 5, 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/remote-gpu-setup/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
- fail: No recursive delete of root, home or parent (matched: rm -r ~/)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2606 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 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
amd-agi/aklr · 15 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lhuhjy4bioewy4if GET https://markdownregistry.com/api/v1/resolve?ref=amd-agi/aklr/remote-gpu-setup GET https://markdownregistry.com/api/v1/blob/0b19ccfbfbc9756bb4c76648931c1238e2d9e1e9a508c614bf48f7420378cdcf
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.