Site Architecture
AvdLee/RocketSimApp
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.
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…
$ npx skills add webcoyote/sandvault --skill sv -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install webcoyote/sandvault sv --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "sv" agent skill from https://github.com/webcoyote/sandvault/tree/main/skills/sandvault/sv into .claude/skills/sv/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sv", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/webcoyote/sandvault/tree/main/skills/sandvault/svType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add webcoyote/sandvault --skill sv -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install webcoyote/sandvault sv --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/webcoyote/sandvault.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sandvault/sv .agents/skills/sv && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sv" agent skill from https://github.com/webcoyote/sandvault/tree/main/skills/sandvault/sv into .agents/skills/sv/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sv", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add webcoyote/sandvault --skill sv -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install webcoyote/sandvault sv --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/webcoyote/sandvault.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sandvault/sv .cursor/skills/sv && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sv" agent skill from https://github.com/webcoyote/sandvault/tree/main/skills/sandvault/sv into .cursor/skills/sv/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sv", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/webcoyote/sandvault.git --path skills/sandvault/sv--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add webcoyote/sandvault --skill sv -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install webcoyote/sandvault sv --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/webcoyote/sandvault.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sandvault/sv .gemini/skills/sv && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sv" agent skill from https://github.com/webcoyote/sandvault/tree/main/skills/sandvault/sv into .gemini/skills/sv/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sv", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install webcoyote/sandvault svInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add webcoyote/sandvault --skill sv -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/webcoyote/sandvault.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sandvault/sv .github/skills/sv && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sv" agent skill from https://github.com/webcoyote/sandvault/tree/main/skills/sandvault/sv into .github/skills/sv/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sv", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add webcoyote/sandvault --skill sv -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install webcoyote/sandvault sv --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/webcoyote/sandvault.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sandvault/sv .opencode/skills/sv && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sv" agent skill from https://github.com/webcoyote/sandvault/tree/main/skills/sandvault/sv into .opencode/skills/sv/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sv", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
svThis 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. 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.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit ad05889. It shows what the files ask for, not the result of running them.
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.
Ships 2 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
brewFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from webcoyote/sandvault at commit ad05889, republished under its Apache-2.0 licence (© webcoyote). 432 words, ~895 tokens.
.claude/skills/sv/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Hand off the current task to a sandboxed Claude running inside sandvault.
The user invokes /sv when they want Claude to continue the current work inside a sandvault sandbox.
Write a clear, actionable summary of what the user wants done. Include:
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:
.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.Show the user:
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):
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
SKILL.md and 2 other files (scripts) in skills/sandvault/sv of webcoyote/sandvault.
Open the folder on GitHubat commit ad05889
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sv this skillwebcoyote/sandvault | 430 | — | ~895 | Automated safety check: Pass | Apache-2.0 | |
| Site ArchitectureAvdLee/RocketSimApp | 803 | 11 repos | ~3.3k | Automated safety check: Pass | Custom licence | |
| Engine Whats Newflutter/flutter | 179k | — | ~978 | Automated safety check: Pass | BSD-3-Clause | |
| macOS Spm App PackagingDimillian/Skills | 4k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Orca iOS Simulator Controlstablyai/orca | 87k | 1 repos | ~584 | Automated safety check: Pass | Apache-2.0 |
AvdLee/RocketSimApp
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.
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).
Dimillian/Skills
Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project.
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.
stablyai/orca
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…
tw93/Mole
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.
Works with
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.