handoff-ticket SKILL.md skillA
handoff-ticket from jeongjaesoon/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jeongjaesoon/agent-skills/handoff-ticket@git:20261104.b533aaePins git:20261104.b533aae in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jeongjaesoon/agent-skills
- Path
skills/handoff-ticket/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261104.b533aae, committed Nov 4, 2026
- First version recorded
- Oct 26, 2026
- Size
- 9,381 bytes
- Repository stars
- 3
- License
- MIT
Use when handing the next ticket to a fresh Orca worktree card — "핸드오프", "다음 티켓 진행해줘", "남은 작업 있어?", "머지하고 다음 진행해줘", "handoff" — and when this session's ticket is done, to decide what runs next. Another repo, or this session keeps working, is dispatch-card.
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
# Orca handoff Finish here, and start each follow-up ticket that stands on its own in its own worktree card (§0 "Who runs it" keeps a small defect in what this session just shipped here). `orca worktree create` is the only way work leaves this session. Ticket operations go through `use-tracker`; the worklog goes through `use-notes`. A handoff always means an Orca worktree card — no other dispatch mechanism. "병렬로 진행" and "동시에 진행" mean this skill only when they name same-repo ticket cards; they can also mean sub-agents or work dispatched while this session continues (dispatch-card), so settle which before creating cards. Not a handoff: the target is another repo, or this session still has its own work to finish after spawning. That is `dispatch-card` — it never closes this session. ## 0. At "done", decide what happens next Done means every acceptance criterion on the ticket is met (`deliver-ticket` §6) — usually the merge plus whatever the ticket asks for after it, such as a release or a verification on main. That last criterion, not the merge commit, is the decision point. **Inside a program.** If this session's brief or prompt has a `PROGRAM: <slug>` line …
Read the whole file at its exact version.
How to install
mdr add jeongjaesoon/agent-skills/handoff-ticket@sha256:3833ce9ed33f10beThe line at the top of this page pins the label git:20261104.b533aae, 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_jy4u7uu37sdgx6iq)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 26, 2026 and Nov 4, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261104.b533aae latest | 2026-11-04 | b533aae | 9,381 B | A | view · diff |
| git:20261101.32d1ec0 | 2026-11-01 | 32d1ec0 | 9,269 B | A | view · diff |
| git:20261101.bf4a8a8 | 2026-11-01 | bf4a8a8 | 9,260 B | A | view · diff |
| git:20261101.1d7600b | 2026-11-01 | 1d7600b | 8,864 B | A | view · diff |
| git:20261026.a9f60bf | 2026-10-26 | a9f60bf | 8,366 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 (9381 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
jeongjaesoon/agent-skills · 3 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jy4u7uu37sdgx6iq GET https://markdownregistry.com/api/v1/resolve?ref=jeongjaesoon/agent-skills/handoff-ticket GET https://markdownregistry.com/api/v1/blob/3833ce9ed33f10be9929ba02dc138f6dae6804b0d8cce68e08546f04378176aa
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.