Agent skill

Sv

by webcoyote in webcoyote/sandvault

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…

Apache-2.0Auto-check passed

Install Sv

skills CLI
$ npx skills add webcoyote/sandvault --skill sv -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install webcoyote/sandvault sv --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/webcoyote/sandvault.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sandvault/sv .claude/skills/sv && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sv
GitHub stars
430
Token cost
~895 tokens
SKILL.md length
432 words
Files
3 (incl. scripts)
Skills in repo
1
Repo updated
First seen
Licence
Apache-2.0

At a glance

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…

  • Works in 4 steps: Summarize the task → Write the handoff file → Ask the user for confirmation → …
  • Asks to hand this off to sandvault
  • SKILL.md covers When to use and Steps
  • Runs Shell scripts from its folder; calls brew

What it does

Sv is an agent skill from webcoyote/sandvault. 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.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/find-terminal-app.sh` and `scripts/launch-in-terminal.sh`).

It works with macOS. The repository describes itself as: Run AI agents isolated in a macOS user account and sandbox-exec. Configured to run Claude Code, OpenAI Codex, Cursor Agent, Google Gemini. The licence is Apache-2.0.

When your agent uses it

  • Asks to hand this off to sandvault
  • Continue in the sandbox
  • Sandvault this task
  • Clone the current repo into a sandboxed Claude session with per-repo deploy-key access

Example prompts

  • “hand this off to sandvault”
  • “continue in the sandbox”
  • “sandvault this task”
  • “/sv”

Requirements

  • A Bash shell

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Summarize the task
  2. Write the handoff file
  3. Ask the user for confirmation
  4. Launch in a new terminal window

What it can do on your machine

Read from SKILL.md and the folder at commit ad05889. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • brew

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sv loads about 895 tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 432 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~895

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from webcoyote/sandvault at commit ad05889, republished under its Apache-2.0 licence (© webcoyote). 432 words, ~895 tokens.

Download SKILL.mdSave it as .claude/skills/sv/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
sv
description
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.

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.

The handoff file should include:

  • A "# Task Handoff" heading
  • Task context, approach, decisions, branch, relevant files
  • 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
3. Ask the user for confirmation

Show the user:

  • The repo that will be cloned
  • A brief summary of the task being handed off
Show full SKILL.md (182 more words)Show less
4. Launch in a new terminal window

Use the bundled helper to launch sv-clone in a new window of whatever terminal the user is running (Terminal.app, iTerm2, Ghostty, WezTerm, kitty, Alacritty, cmux, Warp, with Terminal.app as a fallback):

bash
skills/sandvault/sv/scripts/launch-in-terminal.sh 'sv-clone <repo-path> -- claude -- "Read /Users/Shared/sv-<host-user>/tmp/handoff-<repo>.md and continue the task described there."'

The helper detects the parent terminal app via skills/sandvault/sv/scripts/find-terminal-app.sh (which walks the process tree to find the first ancestor in /Applications) and dispatches to the appropriate launch mechanism for that terminal. To override detection, set SV_TERMINAL (e.g. SV_TERMINAL=ghostty, accepts either a short alias or a .app bundle name).

Substitute <repo-path> (the source repo's absolute path), <host-user> (the host user's login — same $USER used when writing the handoff file), and <repo> (the source repo's basename) literally into the command string.

The launch command runs sv-clone, passing the handoff path to the sandboxed Claude as its initial prompt via the -- separator pass-through (sv-clone → sv → sandbox zshrc → claude).

If sv-clone is not on PATH, the installed sandvault is out of date — tell the user to upgrade (e.g. brew upgrade sandvault) and retry. The old sv --clone flag has been removed in favor of the standalone sv-clone script.

© webcoyote, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in skills/sandvault/sv of webcoyote/sandvault.

  • SKILL.md
  • scripts/find-terminal-app.sh
  • scripts/launch-in-terminal.sh

Open the folder on GitHubat commit ad05889

Compare with similar skills

Sv next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sv compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sv this skillwebcoyote/sandvault430—~895Automated safety check: PassApache-2.0
Site ArchitectureAvdLee/RocketSimApp80311 repos~3.3kAutomated safety check: PassCustom licence
Engine Whats Newflutter/flutter179k—~978Automated safety check: PassBSD-3-Clause
macOS Spm App PackagingDimillian/Skills4k5 repos~1.2kAutomated safety check: PassMIT
Openclaw Live Updateropenclaw/openclaw392k—~3.7kAutomated safety check: PassMIT
Orca iOS Simulator Controlstablyai/orca87k1 repos~584Automated safety check: PassApache-2.0

Similar skills

  • Site Architecture

    AvdLee/RocketSimApp

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.

    803 GitHub starsUsed in 11 repos~3.3k tokens
    Marketing & SEOAuto-check passed
  • Engine Whats New

    flutter/flutter

    Generates the "what's new" release summary and diff file for changes in the Flutter engine (//engine/src/flutter) between two releases (e.g., 3.47 vs 3.44).

    179k GitHub stars~978 tokensUpdated today
    MobileAuto-check passed
  • macOS Spm App Packaging

    Dimillian/Skills

    Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project.

    4k GitHub starsUsed in 5 repos~1.2k tokens
    MobileAuto-check passed
  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • iOS Simulator control from inside Orca, with the live device view in Orca's emulator pane. Use when driving a booted Apple Simulator on macOS: taps, gestures…

    87k GitHub starsUsed in 1 repo~584 tokens
    MobileAuto-check passed
  • A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.

    70k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

Works with

Questions about Sv

What does Sv do?

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…. Sv is an agent skill from webcoyote/sandvault. 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.

When should I use Sv?

Sv fits situations like: asks to hand this off to sandvault; continue in the sandbox; sandvault this task; clone the current repo into a sandboxed Claude session with per-repo deploy-key access.

How do I install Sv in Claude Code?

Run `npx skills add webcoyote/sandvault --skill sv -a claude-code`. Or copy the skill folder (skills/sandvault/sv in webcoyote/sandvault) into .claude/skills/sv in your project. Claude Code loads it when a task matches its description.

How do I install Sv in Codex?

Run `npx skills add webcoyote/sandvault --skill sv -a codex`. Or copy the skill folder (skills/sandvault/sv in webcoyote/sandvault) into .agents/skills/sv in your project. Codex loads it when a task matches its description.

Can I use Sv in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add webcoyote/sandvault --skill sv -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sv, .gemini/skills/sv, .github/skills/sv and .opencode/skills/sv in your project.

What does Sv need to run?

Going by SKILL.md and its folder, Sv needs a shell for the scripts in its folder and the command-line tools its instructions call (brew). Our summary lists: A Bash shell.

Does Sv access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sv safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Sv use?

Sv is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sv use?

About 895 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sv?

Skills that share tags, products or a category with Sv: Site Architecture (AvdLee/RocketSimApp, 803 stars), Engine Whats New (flutter/flutter, 179k stars), macOS Spm App Packaging (Dimillian/Skills, 4k stars) and Openclaw Live Updater (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sv?

webcoyote (a GitHub user) maintains it in webcoyote/sandvault, which has 430 GitHub stars. The repository was last updated on October 4, 2026.

Source: webcoyote/sandvault on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.