cross-repo-handoff SKILL.md skillA
cross-repo-handoff from beakpoint-insights/roost is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add beakpoint-insights/roost/cross-repo-handoff@git:20261026.505a1daPins git:20261026.505a1da in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- beakpoint-insights/roost
- Path
skills/cross-repo-handoff/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.505a1da, committed Oct 26, 2026
- First version recorded
- Oct 26, 2026
- Size
- 3,941 bytes
- Repository stars
- 30
- License
- MIT
Write a prompt that another repo's agent can run cold, for work this repo needs but must not do itself (for example the API change a UI fix depends on, or the UI change an API fix needs). Posts it as a comment on the ticket or returns it for pasting. Use when the user asks for "a prompt for the API agent", "a prompt for the UI agent", "what should I share back", or when a fix needs changes in the other repo.
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
# Cross-Repo Handoff Each repo in the team's roost config (`repos`) has its own agent, often running at the same time. An agent never edits another repo. When a fix needs work over there, write a prompt the other agent can follow with no other context. **First, load the team config with `roost-config`.** Each repo's `owns`, `contract`, `tests` and `e2e` say what belongs where and how it's tested. ## When to write one - Your fix needs a change in the other repo. Finish what belongs to this repo, then write the handoff for the rest. - The other agent asked you for something and you've done it. Write what they need to pick it up (the "share back" note). - The user asks for a prompt to give the other agent. Never edit, build or run tests in the other repo to "check quickly". Reading its code to understand a contract is fine. ## The prompt's shape Write it as plain instructions to another engineer. Use this order and leave out sections that don't apply: …
Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/cross-repo-handoff@sha256:efca85949ed05d90The line at the top of this page pins the label git:20261026.505a1da, 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_5jjzvmq7y3raqrmi)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 26, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.505a1da latest | 2026-10-26 | 505a1da | 3,941 B | A | view · diff |
| git:20261026.66cdcd9 | 2026-10-26 | 66cdcd9 | 3,896 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 (3941 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
beakpoint-insights/roost · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5jjzvmq7y3raqrmi GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/cross-repo-handoff GET https://markdownregistry.com/api/v1/blob/efca85949ed05d90856a4591a3ef138d609e309cefb74c68b4a0279bca259e2b
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.