repo-onboard SKILL.md skillA
repo-onboard from protolabsai/protoagent is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add protolabsai/protoagent/repo-onboard@git:20261016.98e6e56Pins git:20261016.98e6e56 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- protolabsai/protoagent
- Path
plugins/engineer/skills/repo-onboard/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261016.98e6e56, committed Oct 16, 2026
- First version recorded
- Sep 25, 2026
- Size
- 14,744 bytes
- Repository stars
- 17
- License
- MIT
Get the OPERATOR up to speed in an unfamiliar repository fast — clone or register it, find its manifest(s) and README and put them in front of the operator (the README as a markdown artifact, the manifest in the code pane), show the architecture (the repo's Atlas model in `architecture/` when the Atlas plugin is on and the repo has one — else a code-linked Mermaid overview, plus an offer to map it in Atlas), prove the toolchain, write a short repo card, then offer a guided tour one stop per…
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
# Repo onboard Goal: in a few minutes the **operator** knows what the code is, how it runs, and where to look, well enough to explain it. Steps 1–7 are plumbing: do them in **one turn**, then stop with a choice. The tour (step 8) is interactive: one stop per turn. Cite `path:line`. **Never change code during onboarding** — no edits, no writes, no commits. The one exception is the Atlas model (step 9), and only after the operator says yes to it. **Read with the filesystem tools** — `list_dir`, `find_files`, `search_files`, `read_file` — not `execute_code` or ad-hoc scripts: their `file:line` output is what `show_code` and the diagram links need, and they stay inside the project fence. Setup commands go through `run_command`. Every onboarding produces all three views: the README artifact, the manifest in the code pane, and the architecture overview (Atlas or Mermaid, step 5). **Is Atlas here?** If `atlas_validate`, `atlas_describe` and `atlas_show` are bound, the Atlas plugin is on: it renders the repo's LikeC4 model (`architecture/*.c4`) as a drill-down diagram in the console. If they aren't bound, everything below that says …
Read the whole file at its exact version.
How to install
mdr add protolabsai/protoagent/repo-onboard@sha256:3b34301a97d3318bThe line at the top of this page pins the label git:20261016.98e6e56, 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_n5grtlnoxn3mzf7r)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 25, 2026 and Oct 16, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.98e6e56 latest | 2026-10-16 | 98e6e56 | 14,744 B | A | view · diff |
| git:20260926.92196ac | 2026-09-26 | 92196ac | 10,398 B | A | view · diff |
| git:20260925.75b6c26 | 2026-09-25 | 75b6c26 | 5,630 B | A | view |
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 (14744 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
protolabsai/protoagent · 17 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_n5grtlnoxn3mzf7r GET https://markdownregistry.com/api/v1/resolve?ref=protolabsai/protoagent/repo-onboard GET https://markdownregistry.com/api/v1/blob/3b34301a97d3318ba3abef94b7bbad38c44dfa15544adf20cf27b4e051d0e2a5
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.