Vercel Cost Tuning
jeremylongshore/tons-of-skills-marketplace
Optimize Vercel costs through plan selection, function efficiency, and usage monitoring.
Sandbox lifecycle debugging for vercel-openclaw: create, resume, stop, snapshotting, reset, stale-running reconciliation, persistent Sandbox v2 behavior, hot spares, and lifecycle locks.
Install Sandbox Lifecycle Debug
$ npx skills add vercel-labs/vercel-openclaw-archived --skill sandbox-lifecycle-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel-labs/vercel-openclaw-archived sandbox-lifecycle-debug --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/vercel-labs/vercel-openclaw-archived.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/sandbox-lifecycle-debug .claude/skills/sandbox-lifecycle-debug && 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 "sandbox-lifecycle-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/sandbox-lifecycle-debug into .claude/skills/sandbox-lifecycle-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-lifecycle-debug", 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/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/sandbox-lifecycle-debugType 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 vercel-labs/vercel-openclaw-archived --skill sandbox-lifecycle-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel-labs/vercel-openclaw-archived sandbox-lifecycle-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/vercel-openclaw-archived.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/sandbox-lifecycle-debug .agents/skills/sandbox-lifecycle-debug && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sandbox-lifecycle-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/sandbox-lifecycle-debug into .agents/skills/sandbox-lifecycle-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-lifecycle-debug", 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 vercel-labs/vercel-openclaw-archived --skill sandbox-lifecycle-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel-labs/vercel-openclaw-archived sandbox-lifecycle-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/vercel-openclaw-archived.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/sandbox-lifecycle-debug .cursor/skills/sandbox-lifecycle-debug && 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 "sandbox-lifecycle-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/sandbox-lifecycle-debug into .cursor/skills/sandbox-lifecycle-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-lifecycle-debug", 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/vercel-labs/vercel-openclaw-archived.git --path .agents/skills/sandbox-lifecycle-debug--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 vercel-labs/vercel-openclaw-archived --skill sandbox-lifecycle-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel-labs/vercel-openclaw-archived sandbox-lifecycle-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/vercel-openclaw-archived.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/sandbox-lifecycle-debug .gemini/skills/sandbox-lifecycle-debug && 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 "sandbox-lifecycle-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/sandbox-lifecycle-debug into .gemini/skills/sandbox-lifecycle-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-lifecycle-debug", 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 vercel-labs/vercel-openclaw-archived sandbox-lifecycle-debugInstalls 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 vercel-labs/vercel-openclaw-archived --skill sandbox-lifecycle-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vercel-labs/vercel-openclaw-archived.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/sandbox-lifecycle-debug .github/skills/sandbox-lifecycle-debug && 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 "sandbox-lifecycle-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/sandbox-lifecycle-debug into .github/skills/sandbox-lifecycle-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-lifecycle-debug", 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 vercel-labs/vercel-openclaw-archived --skill sandbox-lifecycle-debug -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vercel-labs/vercel-openclaw-archived sandbox-lifecycle-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/vercel-openclaw-archived.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/sandbox-lifecycle-debug .opencode/skills/sandbox-lifecycle-debug && 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 "sandbox-lifecycle-debug" agent skill from https://github.com/vercel-labs/vercel-openclaw-archived/tree/main/.agents/skills/sandbox-lifecycle-debug into .opencode/skills/sandbox-lifecycle-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-lifecycle-debug", 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.
Facts
- Skill name
sandbox-lifecycle-debug- GitHub stars
- 117
- Token cost
- ~809 tokens
- SKILL.md length
- 310 words
- Files
- 1
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- MIT
At a glance
Sandbox lifecycle debugging for vercel-openclaw: create, resume, stop, snapshotting, reset, stale-running reconciliation, persistent Sandbox v2 behavior, hot spares, and lifecycle locks.
- Sandbox state transitions
- SKILL.md covers Start Here, Split The State, Common Paths and Sandbox v2 Rules, plus 2 more sections
- Calls git and node
- Lifecycle recovery is wrong
What it does
Sandbox Lifecycle Debug is an agent skill from vercel-labs/vercel-openclaw-archived, published by the product's own GitHub organization. Sandbox lifecycle debugging for vercel-openclaw: create, resume, stop, snapshotting, reset, stale-running reconciliation, persistent Sandbox v2 behavior, hot spares, and lifecycle locks. Use when sandbox state transitions, status polling, stop/resume, reset, or lifecycle recovery is wrong.
Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Accounting and bookkeeping and Debugging. It works with Vercel. The repository describes itself as: Deploy OpenClaw on Vercel. The licence is MIT.
When your agent uses it
- Sandbox state transitions
- Lifecycle recovery is wrong
Example prompts
- “/sandbox-lifecycle-debug”
What it can do on your machine
Read from SKILL.md and the folder at commit d592f7b. 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
Shell commands in SKILL.md call:
gitnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Sandbox Lifecycle Debug loads about 809 tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 310 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.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from vercel-labs/vercel-openclaw-archived at commit d592f7b, republished under its MIT licence (© vercel-labs). 310 words, ~809 tokens.
Download SKILL.mdSave it as
.claude/skills/sandbox-lifecycle-debug/SKILL.md (or your agent's skills folder).- name
- sandbox-lifecycle-debug
- description
- Sandbox lifecycle debugging for vercel-openclaw: create, resume, stop, snapshotting, reset, stale-running reconciliation, persistent Sandbox v2 behavior, hot spares, and lifecycle locks. Use when sandbox state transitions, status polling, stop/resume, reset, or lifecycle recovery is wrong.
Sandbox Lifecycle Debug
Use this skill when the sandbox state machine is the primary suspect.
For Sandbox v2 truth-model work, also load sandbox-v2-lifecycle. Official Vercel Sandbox v2 docs override older repo guidance that treats manual snapshots as the normal restore source.
Start Here
Read lat.md/sandbox-lifecycle.md sections Status State Machine, Triggers -- What Causes State Transitions, and the specific trigger involved. Run lat locate "Sandbox Lifecycle" or lat search "sandbox lifecycle <symptom>" when unsure.
Collect before edits:
GET /api/statusand any UI state that triggered the action.GET /api/admin/sandbox-diag.GET /api/admin/logsfiltered forsandbox.,gateway.,watchdog.,proxy..- Local
git rev-parse HEAD, remotegit ls-remote origin main, and live deployment proof.
Split The State
Report these separately:
- metadata status in
SingleMeta.status - Vercel Sandbox SDK status
- gateway readiness on port 3000
- persistent auto-saved state availability
- manual snapshot/checkpoint availability when relevant
- lifecycle lock and start lock state when visible
- UI polling status
Do not use running as shorthand for gateway-ready or user-ready.
Common Paths
- Admin ensure:
/api/admin/ensure->ensureSandboxRunning()/ensureSandboxReady(). - Gateway request: auth ->
ensureSandboxRunning()-> token refresh ->touchRunningSandbox()-> proxy. - Stop/auto-save:
stopSandbox()-> cleanup -> cron persistence ->sandbox.stop({ blocking: false })->snapshottinghost metadata while v2 persists state. - Status polling:
GET /api/status-> stale running or snapshotting reconciliation. - Reset:
resetSandbox()destroys active sandbox and snapshots, clears cron and token metadata.
Sandbox v2 Rules
- Main OpenClaw sandbox is one named persistent sandbox.
- Normal resume uses the persistent name and auto-saved state, not manual
snapshotId. - Observation of stopped/snapshotting state must use
resume:false. - Manual
snapshot()is explicit/debug/checkpoint only and shuts the sandbox down. - Worker/debug sandboxes are short-lived and must use
persistent:false.
Fix Boundaries
- Primary:
src/server/sandbox/lifecycle.ts,src/server/sandbox/controller.ts. - Routes:
src/app/api/admin/{ensure,stop,snapshot,reset,status}/**andsrc/app/api/status/route.ts. - Tests: lifecycle and harness tests under
src/server/sandbox/**.test.tsandsrc/test-utils/harness. - Docs:
lat.md/sandbox-lifecycle.md,docs/lifecycle-and-restore.md.
Verification
Use the narrowest command that covers the path, then run the repo verifier when the change has broad lifecycle impact:
node scripts/verify.mjs --steps=test,typecheck
lat checkFor live lifecycle incidents, include before/after /api/status, /api/admin/sandbox-diag, and relevant log events.
© vercel-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/sandbox-lifecycle-debug of vercel-labs/vercel-openclaw-archived.
Open the folder on GitHubat commit d592f7b
Compare with similar skills
Sandbox Lifecycle Debug 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 |
|---|---|---|---|---|---|---|
| Sandbox Lifecycle Debug this skillvercel-labs/vercel-openclaw-archived | 117 | — | ~809 | Automated safety check: Pass | MIT | |
| Vercel Cost Tuningjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Claudeceptiondivinevideo/divine-mobile | 266 | — | ~1.1k | Automated safety check: Pass | MIT | |
| QA Find Bugs CLIbex-co/beancount-io | 295 | — | ~2.2k | Automated safety check: Notes | MIT | |
| Mistral Reference Architecturejeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~932 | Automated safety check: Pass | MIT | |
| Mistral SDK Patternsjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~853 | Automated safety check: Pass | MIT |
Similar skills
Claudeception
divinevideo/divine-mobile
A skill your agent uses when reviewing what was learned after debugging, workaround discovery, or trial-and-error investigation, and capture it as a dated journal entry under ~/.codex/journal
QA Find Bugs CLI
bex-co/beancount-io
Hunt bugs in the Beancount.io bea CLI by running real commands against isolated synthetic ledgers, checking output and file effects, reproducing failures, tracing root causes, and deduplicating…
Mistral Reference Architecture
jeremylongshore/tons-of-skills-marketplace
Design a Mistral integration from policy gateway through adapter, queues, state reconciliation, and audited output.
Mistral SDK Patterns
jeremylongshore/tons-of-skills-marketplace
Design a pinned Mistral client adapter with typed results, cancellation, retry classification, and usage accounting.
Odoo Agency Fleet Review
erpipe-org/mcp-odoo
Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…
More from vercel-labs/vercel-openclaw-archived
All 16 skills in this repo- Official
Channel Debug Core
vercel-labs/vercel-openclaw-archived
Channel webhook triage for vercel-openclaw Slack/Telegram/Discord/WhatsApp issues: prove deployment state, collect admin readiness endpoints, build evidence-first handoff before fixes.
- Official
Lat Md
vercel-labs/vercel-openclaw-archived
Writing and maintaining lat.md documentation files — structured markdown that describes a project's architecture, design decisions, and test specs.
- Official
Cron Watchdog Debug
vercel-labs/vercel-openclaw-archived
Cron and watchdog debugging for vercel-openclaw: Vercel Cron auth, persisted OpenClaw jobs, cron wake keys, token refresh, restore oracle, hot spare, and watchdog reports.
- Official
Auth Store Debug
vercel-labs/vercel-openclaw-archived
Auth and store debugging for vercel-openclaw: admin-secret mode, Sign in with Vercel, session cookies, CSRF, LOCALREADONLY, Redis vs memory store, keyspace namespacing, and metadata shape migrations.
- Official
Firewall AI Gateway Debug
vercel-labs/vercel-openclaw-archived
Firewall and Vercel AI Gateway debugging for vercel-openclaw: network policy allowlists, OIDC token refresh, AI Gateway transform rules, firewall learning/enforcement, and sandbox.update…
- Official
Gateway Proxy Debug
vercel-labs/vercel-openclaw-archived
Gateway and proxy debugging for vercel-openclaw: /gateway routing, HTML injection, WebSocket rewrite, gateway-token handoff, waiting page, status heartbeat, sandbox port URL cache, and proxy auth.
Related
Works with
Categories
Questions about Sandbox Lifecycle Debug
What does Sandbox Lifecycle Debug do?
Sandbox lifecycle debugging for vercel-openclaw: create, resume, stop, snapshotting, reset, stale-running reconciliation, persistent Sandbox v2 behavior, hot spares, and lifecycle locks. Sandbox Lifecycle Debug is an agent skill from vercel-labs/vercel-openclaw-archived, published by the product's own GitHub organization. Sandbox lifecycle debugging for vercel-openclaw: create, resume, stop, snapshotting, reset, stale-running reconciliation, persistent Sandbox v2 behavior, hot spares, and lifecycle locks.
When should I use Sandbox Lifecycle Debug?
Sandbox Lifecycle Debug fits situations like: sandbox state transitions; lifecycle recovery is wrong.
How do I install Sandbox Lifecycle Debug in Claude Code?
Run `npx skills add vercel-labs/vercel-openclaw-archived --skill sandbox-lifecycle-debug -a claude-code`. Or copy the skill folder (.agents/skills/sandbox-lifecycle-debug in vercel-labs/vercel-openclaw-archived) into .claude/skills/sandbox-lifecycle-debug in your project. Claude Code loads it when a task matches its description.
How do I install Sandbox Lifecycle Debug in Codex?
Run `npx skills add vercel-labs/vercel-openclaw-archived --skill sandbox-lifecycle-debug -a codex`. Or copy the skill folder (.agents/skills/sandbox-lifecycle-debug in vercel-labs/vercel-openclaw-archived) into .agents/skills/sandbox-lifecycle-debug in your project. Codex loads it when a task matches its description.
Can I use Sandbox Lifecycle Debug 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 vercel-labs/vercel-openclaw-archived --skill sandbox-lifecycle-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sandbox-lifecycle-debug, .gemini/skills/sandbox-lifecycle-debug, .github/skills/sandbox-lifecycle-debug and .opencode/skills/sandbox-lifecycle-debug in your project.
What does Sandbox Lifecycle Debug need to run?
Going by SKILL.md and its folder, Sandbox Lifecycle Debug needs the command-line tools its instructions call (git and node).
Does Sandbox Lifecycle Debug access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Sandbox Lifecycle Debug 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. Review the folder before installing.
What licence does Sandbox Lifecycle Debug use?
Sandbox Lifecycle Debug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sandbox Lifecycle Debug use?
About 809 tokens (SKILL.md is roughly 3.2k 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 Sandbox Lifecycle Debug?
Skills that share tags, products or a category with Sandbox Lifecycle Debug: Vercel Cost Tuning (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Claudeception (divinevideo/divine-mobile, 266 stars), QA Find Bugs CLI (bex-co/beancount-io, 295 stars) and Mistral Reference Architecture (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sandbox Lifecycle Debug?
vercel-labs (a GitHub organization, an official publisher) maintains it in vercel-labs/vercel-openclaw-archived, which has 117 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on May 15, 2026.
Source: vercel-labs/vercel-openclaw-archived on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.