rpi SKILL.md skillA
rpi from humanlayer/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add humanlayer/skills/rpi@git:20261031.18cb28fPins git:20261031.18cb28f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- humanlayer/skills
- Path
plugins/rpi/skills/rpi/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261031.18cb28f, committed Oct 31, 2026
- First version recorded
- Oct 7, 2026
- Size
- 5,358 bytes
- Repository stars
- 5,828
- License
- MIT
Only use when the user explicitly invokes this skill by name.
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
# Research, Design, and Implement Help the user research a change, work through its design, and implement it. Follow their requested step, using the phase instructions below. `$SKILLBASE` means the directory containing this `SKILL.md`. `<rpi-invocation>` in templates means the host's skill command: `$rpi` in Codex, `/rpi` in Claude Code, or its plugin-qualified name when the host exposes one. Render next commands with that native invocation. ## Choose the Step Follow the user's requested step. Read `$SKILLBASE/references/workflow.md` when choosing or explaining a flow or what comes next. For a task description with no requested step, start with research questions. Ask which flow the user wants: research followed by design discussion, PRD, or TDD, or research only. Wait for their choice before starting the phase, then carry it into suggested next commands. When asking the user to choose a flow, read `$SKILLBASE/references/workflow-choice.md` and show its box-and-line chart with the question. Create writes a new document; iterate updates an existing document in place using the user's feedback or resumes the workflow for a partially finished document. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_a3pr2parthcl5h56/82c68bba346022d3ef32d8887fc6fb4f94a339f63b92186886c453e813d45333.json
Then /plugin install rpi@markdownregistry-a3pr2parthcl5h56 in Claude Code. It installs git:20261031.18cb28f, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add humanlayer/skills/rpi@sha256:82c68bba346022d3The line at the top of this page pins the label git:20261031.18cb28f, 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_a3pr2parthcl5h56)
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 humanlayer/skills/rpi 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 rpi from somewhere else? Ask it: where did my rpi 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 Oct 7, 2026 and Oct 31, 2026, about one every 6 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261031.18cb28f latest | 2026-10-31 | 18cb28f | 5,358 B | A | view · diff |
| git:20261008.9454f32 | 2026-10-08 | 9454f32 | 4,930 B | A | view · diff |
| git:20261008.8276a26 | 2026-10-08 | 8276a26 | 4,923 B | A | view · diff |
| git:20261008.ada4a55 | 2026-10-08 | ada4a55 | 4,791 B | A | view · diff |
| git:20261007.04ecf04 | 2026-10-07 | 04ecf04 | 4,429 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/rpi/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 (5358 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
humanlayer/skills · 5,828 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_a3pr2parthcl5h56 GET https://markdownregistry.com/api/v1/resolve?ref=humanlayer/skills/rpi GET https://markdownregistry.com/api/v1/blob/82c68bba346022d3ef32d8887fc6fb4f94a339f63b92186886c453e813d45333
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 humanlayer/skills
Every file in humanlayer/skills