daytona-dev — Claude Code skill: Daytona cloud sandbox
daytona-dev — a skill for Claude Code and Codex that sets up a Daytona cloud sandbox running an XFCE/noVNC desktop. The iPolloWork Electron app becomes accessible through the browser at port 6080.
LicenseRef-Proprietary ★ 7,523 updated 2026-10-29
npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a claude-codeWhat daytona-dev does
The skill targets Claude Code and Codex. It covers creating a Daytona sandbox that runs the iPolloWork Electron app on a full XFCE desktop, exposed through noVNC so the UI is reachable in any browser.
Seven components are defined: test-on-daytona.sh for the Electron/noVNC/CDP session, test-server-on-daytona.sh for the cloud server sandbox, daytona-chrome-cdp for a standalone Chrome instance, the ipollowork-eval-secrets:/daytona-secrets and ipollowork-eval-artifacts:/daytona-artifacts volumes for provider keys and screenshots, and the companion skills fraimz and daytona-electron-den. Den API on port 8788 and Den Web on port 3005 only start when MySQL is present — the raw Daytona sandbox without Docker Compose has none.
Setup requires the Daytona CLI, an active login, and a selected organization. Pass --disk 10 when creating the sandbox: the default disk allocation is too small for iPolloWork dependencies and sidecar preparation. Avoid --context . — it uploads the entire repo including node_modules.
What it helps with
- Run the iPolloWork Electron app inside a Daytona cloud sandbox
- Access the XFCE desktop through noVNC in a browser
- Connect to Electron via CDP for UI automation and testing
- Store screenshots and validation artifacts in a dedicated volume
- Restart Vite or Electron inside a running sandbox without rebuilding it
Example prompts for the agent
- Create the sandbox and start iPolloWork with
bash .devcontainer/test-on-daytona.sh - Retrieve the noVNC URL by running
daytona preview-url ipollowork-dev -p 6080 - Tail Electron logs inside the sandbox with
daytona exec ipollowork-dev 'tail -50 /tmp/electron.log'
How to install daytona-dev
1Skills CLI (Vercel)
npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a claude-code2Manually: put the files in place
~/.claude/skills/daytona-dev/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/daytona-dev/
1Skills CLI (Vercel)
npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a codex2Manually: put the files in place
.agents/skills/daytona-dev/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a cursor2Manually: put the files in place
.cursor/skills/daytona-dev/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Devin-AXIS/iPolloWork .opencode/skills/daytona-dev2Manually: put the files in place
.github/skills/daytona-dev/SKILL.md1Skills CLI (Vercel)
npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a gemini-cli2Platform CLI
gemini skills install https://github.com/Devin-AXIS/iPolloWork --path .opencode/skills/daytona-devManually: put the files in place
.devin/skills/daytona-dev/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about daytona-dev
How do I install daytona-dev in Claude Code?
Run npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a claude-code. The skill file lands at ~/.claude/skills/daytona-dev/SKILL.md.
What does the daytona-dev skill do?
It describes the full Daytona environment for iPolloWork: how to create a sandbox, start Electron with noVNC and CDP, and which volumes to mount for secrets and artifacts.
Why don't Den API and Den Web start in the Daytona sandbox?
Both services require MySQL. Without Docker Compose, MySQL is not available in the raw Daytona sandbox, so ports 8788 and 3005 stay silent. Use docker-compose.yml with Docker-in-Docker, or tunnel from a local Den instance.