repo-handoff SKILL.md skillB
repo-handoff from eagerworks/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add eagerworks/skills/repo-handoff@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- eagerworks/skills
- Path
skills/repo-handoff/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Sep 12, 2026
- Size
- 9,158 bytes
- Repository stars
- 15
- License
- MIT
Analyzes a codebase being inherited from another team or company and produces a handoff report — what the code reveals about architecture, setup, deploy, data, third-party services, access, code health, process, and operations — plus a prioritized list of questions the previous team must answer before they leave. Use when asked "we're taking over this repo", "prepare the handoff for this project", "what do we need to ask the previous team", "audit this inherited codebase…
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 Handoff Skill A **handoff** is the moment a codebase changes hands: one team stops owning it, another starts. Most of what the outgoing team knows is not in the repo — which account owns the DNS, why that migration was never run, which cron job must not overlap, who gets paged. This skill reads the repo from the **receiving team's** point of view, records everything the code *does* answer, and turns everything it *doesn't* into a concrete, prioritized list of questions for the previous team — so the knowledge-transfer meeting is spent on the real gaps, not on things `grep` could have told you. The analysis is **read-only with exactly one write**: the finished report is printed in chat **and** saved to `docs/repo-handoff.md` at the analyzed repo's root (`docs/` is created if missing; the file is overwritten on re-run, preserving answers already filled in). Nothing else is created, edited, committed, or pushed. ## Discovery — Do This First Classify the project before analyzing anything. Every check in `references/dimensions.md` depends on knowing the stack and where things live. …
Read the whole file at its exact version.
How to install
mdr add eagerworks/skills/repo-handoff@sha256:db41e5d947a2d4f0The line at the top of this page pins the label v1.0.0, 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_4o6hwwd5b2vi6upc)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 12, 2026.
Audit of the latest version
- fail: No instruction to read or print local credentials (matched: print a secret's value.** If `.env)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9158 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 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
eagerworks/skills · 15 stars · license MIT · pushed 2026-09-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4o6hwwd5b2vi6upc GET https://markdownregistry.com/api/v1/resolve?ref=eagerworks/skills/repo-handoff GET https://markdownregistry.com/api/v1/blob/db41e5d947a2d4f0c127b70e24e642d374cc383c7657521526f87ddd08c676a9
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 eagerworks/skills
Every file in eagerworks/skills