Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sangrokjung/relay
Session relay — compresses what's been done so far (writes a one-liner for /compact) and generates a "next task" prompt (a baton) for the user to hand off.
Passed 9 of 16 test cases with the skill, and 5 of 16 without it.
and 5 more in the full report
8 fixed5 passed either way7 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
If the auto-restore hook fires after context compaction, how many times does it inject the saved carryover baton pointer?
| Checked | Without skill | With skill |
|---|---|---|
| Injects the carryover pointer exactly once before consuming or clearing it. | Missed | Passed |
The instructions your model reads when the skill loads.
Think of a relay race: the runner hands off the baton before stopping. Before context fills up, this skill produces two things: ① a one-line
/compactcommand that compresses everything so far, and ② a handoff document (a "baton") that lets the next session start running immediately on the next task.
When: context is 70%+ used, work is about to be interrupted, or the user asks to "relay / hand off / next session / baton / handoff."
Important (invariant): this skill never runs /compact directly (a skill cannot execute /compact).
It only produces the one-liner the user pastes in.
Let $SKILL be the absolute path of the directory containing this SKILL.md. Scripts live in $SKILL/scripts/.
From $ARGUMENTS:
--new-session (for a brand-new session — instructs the user to paste the whole baton), --no-ask (skip the clarifying question), --quick (skip prose, skeleton only), --copy (opt-in clipboard copy — off by default, see §6).Run bash "$SKILL/scripts/relay-collect.sh" → capture one JSON object. (facts about git/plan/session-summary/tasks/artifacts)
This JSON is the source of truth for every "fact." Do not retype it from memory — quote it verbatim.
If NEXT_TASK is empty and --no-ask was not passed, ask one AskUserQuestion:
"What's the first thing to do next?" — options pulled from plan.next_unchecked / session_summary.next_steps
/ tasks.items in the collect JSON, plus "type it myself." Tag the answer [from-user].
/compact one-linerbash "$SKILL/scripts/relay-build-focus.sh" "<NEXT_TASK>" "<files>" "<decision>"
<files> = key files relevant to the next task (space/comma separated, optional).<decision> = one line capturing a key decision to preserve (optional).bash "$SKILL/scripts/relay-write-baton.sh" "<NEXT_TASK>" <path-to-collect.json or -> "<focus line>"
-.--quick)test cases passed, vs 5 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.