This skill should be used when the user invokes `/sv` or asks to "hand this off to sandvault", "continue in the sandbox", "sandvault this task", or to clone the current repo into a sandboxed Claude session with per-repo deploy-key access. Writes a task briefing to the sandvault shared workspace and launches `sv-clone` in a new terminal window, pointing the sandboxed Claude at the briefing as its first prompt.
SkillScore68Maintained
Automatic
◆Coding pack
Last verified 8/22/2026
What it changes
Passed 13 of 19 test cases with the skill, and 5 of 19 without it.
Without skill27%
With skill68%
Checks it passed that the model alone missed
Specifies the SV_TERMINAL environment variable.
Specifies '# Task Handoff' as the main heading.
States that nothing is written into the source repo itself.
and 7 more in the full report
10 fixed5 passed either way6 still failing1 broke
Pass-rate lift
+41 pp
Tokens
-2%
Agent turns
0%
Response time
-60%
Model gemini-3.6-flashMeasured 8/22/2026v115 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
What main top-level heading must start the written handoff briefing file?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies '# Task Handoff' as the main heading.
Missed
Passed
case-14 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md69 lines3 filesincludes scripts
Sandvault Handoff
Hand off the current task to a sandboxed Claude running inside sandvault.
When to use
The user invokes /sv when they want Claude to continue the current work inside a sandvault sandbox.
Steps
1. Summarize the task
Write a clear, actionable summary of what the user wants done. Include:
What the goal is
What approach to take (if already discussed)
What files are involved
Any decisions already made in this conversation
The current branch name and any relevant context
2. Write the handoff file
Write the task briefing to /Users/Shared/sv-$USER/tmp/handoff-<repo>.md,
where $USER is the host user and <repo> is the source repo's
basename (e.g. /Users/Shared/sv-jesse/handoff-sandvault.md). This is
the sandvault shared workspace — readable from inside the sandbox via
the mounted /Users/Shared tree, so the sandboxed Claude can read it
at startup. The briefing is not copied into the clone; it lives in
the shared workspace and the sandboxed Claude is pointed at it by path
(see step 4). Nothing is written into the source repo itself.
A "## Setup" section: note that gitignored build artifacts (.venv/, node_modules/, build dirs) won't be in the clone. Check for requirements.txt, pyproject.toml, package.json etc. and instruct the sandboxed Claude to set up the environment first.
A "## What to do" section with a direct instruction