Agent skill

Daytona Sandbox Operations

by different-ai in different-ai/openwork

Covers Daytona CLI setup, sandbox debugging, keeping a sandbox alive and which credentials the CLI uses, for when Daytona itself is the problem rather than the tests.

Custom licenceAuto-check passedDevOps & Cloud

Install Daytona Sandbox Operations

skills CLI
$ npx skills add different-ai/openwork --skill daytona -a claude-code

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

GitHub CLI
$ gh skill install different-ai/openwork daytona --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/different-ai/openwork.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/daytona .claude/skills/daytona && 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
daytona
GitHub stars
24k
Token cost
~917 tokens
SKILL.md length
403 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
Custom licence

At a glance

Covers Daytona CLI setup, sandbox debugging, keeping a sandbox alive and which credentials the CLI uses, for when Daytona itself is the problem rather than the tests.

  • Setting up and authenticating the Daytona CLI
  • SKILL.md covers Setup, Long-lived manual Electron…, Long-lived manual server sandbox and Debugging, plus 3 more sections
  • Calls bash, brew and pnpm; needs DAYTONA_API_KEY
  • Debugging a Daytona sandbox that fails with a memory-limit error

What it does

This skill is for Daytona infrastructure problems, not for deciding where tests run. Setup means installing the CLI with Homebrew and running daytona login. Much of the content explains which identity the CLI uses: the DAYTONA_API_KEY variable counts only when DAYTONA_API_URL is also set, otherwise the CLI silently falls back to the saved profile in its config directory, which you can point at an empty folder to test the not-logged-in path.

It warns against running daytona login with an API key on someone else's machine for a one-off task, since that overwrites their profile and browser login, and describes a personal-organization trap: a personal org has a 10 GiB total memory cap and none of the team's warm snapshots, so multi-sandbox previews fail with a memory-limit error. A CLI and API version mismatch warning is usually harmless. A devcontainer helper script starts long-lived manual Electron sandboxes, and test runs are redirected to a separate pnpm evals command.

When your agent uses it

  • Setting up and authenticating the Daytona CLI
  • Debugging a Daytona sandbox that fails with a memory-limit error
  • Keeping a Daytona sandbox alive for manual exploration

Example prompts

  • “Install the Daytona CLI and log in so I can create sandboxes.”
  • “My multi-sandbox preview fails with a memory-limit error on Daytona, so check which organization I am logged into.”
  • “Why does the Daytona CLI ignore my DAYTONA_API_KEY?”

Requirements

  • Homebrew to install the Daytona CLI
  • A Daytona account

What it can do on your machine

Read from SKILL.md and the folder at commit 9ce20f8. 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:

    • bash
    • brew
    • pnpm

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm, 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 these keys or tokens, usually read from environment variables:

    • DAYTONA_API_KEY

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

Context cost

Daytona Sandbox Operations loads about 917 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 403 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 403 words (~917 tokens).

“Use this skill for Daytona infrastructure, not test placement.”

— opening of SKILL.md by different-ai, Custom licence
name
daytona

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .opencode/skills/daytona of different-ai/openwork.

Open the folder on GitHubat commit 9ce20f8

Compare with similar skills

Daytona Sandbox Operations 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.

Daytona Sandbox Operations compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Daytona Sandbox Operations this skilldifferent-ai/openwork24k—~917Automated safety check: PassCustom licence
CodexBar macOS Releasesteipete/CodexBar22k—~1.5kAutomated safety check: PassMIT
Debugsbusso/claudeclaw1941 repos~3.3kAutomated safety check: NotesMIT
Dotenvx Secretskortix-ai/suna20k—~4.2kAutomated safety check: NotesCustom licence
CLI Channel Debuggingmicrosoft/aspire6.3k—~6.4kAutomated safety check: PassMIT
China Mirror ResolverLeoYeAI/openclaw-master-skills2.2k—~4.6kAutomated safety check: NotesMIT

Similar skills

  • CodexBar macOS Release

    steipete/CodexBar

    Releases a signed, notarized CodexBar build: confirms the changelog, resolves signing credentials from 1Password, runs the release script in tmux, and updates the Sparkle appcast and Homebrew tap.

    22k GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Debug

    sbusso/claudeclaw

    Debug container agent issues. An agent skill from sbusso/claudeclaw.

    194 GitHub starsUsed in 1 repo~3.3k tokens
    DevOps & CloudAuto-check: notes
  • Dotenvx Secrets

    kortix-ai/suna

    How this repo manages API secrets and the four local-run environments (local/dev/staging/prod).

    20k GitHub stars~4.2k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • CLI Channel Debugging

    microsoft/aspire

    Official

    Emulates any Aspire CLI build identity (channel, version, commit, package source) from a locally built CLI using ASPIRECLI environment variables and the install sidecar, so a reported bug can be…

    6.3k GitHub stars~6.4k tokensUpdated today
    DevelopmentAuto-check passed
  • China Mirror Resolver

    LeoYeAI/openclaw-master-skills

    Self-healing China mirror source resolver. An agent skill from LeoYeAI/openclaw-master-skills.

    2.2k GitHub stars~4.6k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check: notes
  • Local Dev Setup

    mohitagw15856/pm-claude-skills

    Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running…

    1.4k GitHub stars~4.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

More from different-ai/openwork

All 33 skills in this repo
  • OpenWork Desktop CDP Driver

    different-ai/openwork

    Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.

    24k GitHub stars~465 tokensUpdated today
    Auto-check passed
  • Fake Model Provider Faults

    different-ai/openwork

    Makes the desktop app's model provider fail on demand, with refused connections, resets, stalls and HTTP 4xx and 5xx errors, so error and retry states can be reproduced.

    24k GitHub stars~642 tokensUpdated today
    Auto-check passed
  • OpenWork Model Alias Manager

    different-ai/openwork

    Manages OpenWork's inference model aliases, discounts and overlays over the upstream OpenRouter catalog, and triggers the GitHub workflow that refreshes base models.

    24k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Reproduce Chat States

    different-ai/openwork

    Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.

    24k GitHub stars~673 tokensUpdated today
    Auto-check passed
  • Attaches OpenCode browser tools to the OpenWork Electron dev app through CDP to explore its UI, send a composer task and debug, not to give test verdicts.

    24k GitHub stars~780 tokensUpdated today
    Auto-check passed
  • Daytona Seeded Cloud Demo

    different-ai/openwork

    Spins up a persistent OpenWork Cloud Den demo on a Daytona sandbox, seeds it with Acme Robotics data and returns shareable URLs and login details.

    24k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Works with

Questions about Daytona Sandbox Operations

What does Daytona Sandbox Operations do?

Covers Daytona CLI setup, sandbox debugging, keeping a sandbox alive and which credentials the CLI uses, for when Daytona itself is the problem rather than the tests. This skill is for Daytona infrastructure problems, not for deciding where tests run. Setup means installing the CLI with Homebrew and running daytona login.

When should I use Daytona Sandbox Operations?

Daytona Sandbox Operations fits situations like: setting up and authenticating the Daytona CLI; debugging a Daytona sandbox that fails with a memory-limit error; keeping a Daytona sandbox alive for manual exploration.

How do I install Daytona Sandbox Operations in Claude Code?

Run `npx skills add different-ai/openwork --skill daytona -a claude-code`. Or copy the skill folder (.opencode/skills/daytona in different-ai/openwork) into .claude/skills/daytona in your project. Claude Code loads it when a task matches its description.

How do I install Daytona Sandbox Operations in Codex?

Run `npx skills add different-ai/openwork --skill daytona -a codex`. Or copy the skill folder (.opencode/skills/daytona in different-ai/openwork) into .agents/skills/daytona in your project. Codex loads it when a task matches its description.

Can I use Daytona Sandbox Operations 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 different-ai/openwork --skill daytona -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/daytona, .gemini/skills/daytona, .github/skills/daytona and .opencode/skills/daytona in your project.

What does Daytona Sandbox Operations need to run?

Going by SKILL.md and its folder, Daytona Sandbox Operations needs the command-line tools its instructions call (bash, brew and pnpm) and credentials named DAYTONA_API_KEY. Our summary lists: Homebrew to install the Daytona CLI; A Daytona account.

Does Daytona Sandbox Operations 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 Daytona Sandbox Operations 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 Daytona Sandbox Operations use?

Daytona Sandbox Operations has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Daytona Sandbox Operations use?

About 917 tokens (SKILL.md is roughly 3.7k 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 Daytona Sandbox Operations?

Skills that share tags, products or a category with Daytona Sandbox Operations: CodexBar macOS Release (steipete/CodexBar, 22k stars), Debug (sbusso/claudeclaw, 194 stars), Dotenvx Secrets (kortix-ai/suna, 20k stars) and CLI Channel Debugging (microsoft/aspire, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Daytona Sandbox Operations?

different-ai (a GitHub organization) maintains it in different-ai/openwork, which has 23,943 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 8, 2026.

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