daytona-electron-den — Claude Code skill: Electron against Den
daytona-electron-den runs a real Electron build against a Den server in two Daytona sandboxes, then collects proof: health checks, bootstrap state, screenshots and a recording.
LicenseRef-Proprietary ★ 7,523 updated 2026-10-29
npx skills add Devin-AXIS/iPolloWork --skill daytona-electron-den -a claude-codeWhat daytona-electron-den does
The skill runs an end-to-end pass over two Daytona sandboxes. One hosts Den, the other hosts the real Electron build pointed at that server rather than production. The server side starts with .devcontainer/test-server-on-daytona.sh <branch-or-commit>; keep the printed SERVER_SANDBOX, DEN_WEB_URL, DEN_API_URL and DEN_WORKER_PROXY_URL, then hit /api/den/health and /health with curl -sf to see whether it is alive.
On the client side, .devcontainer/test-on-daytona.sh <branch-or-commit> takes --den-base-url, --den-api-base-url and --artifacts-volume. Add --require-signin when the window has to stay logged out until cloud auth finishes. Add --record-video --recording-name <name> when a pull request needs a recording.
Before any cloud feature is tested, check desktop-bootstrap.json: baseUrl and apiBaseUrl must resolve to the sandbox, not production. A browser redirect is not proof of desktop auth, because the handoff URL is minted by the Den API and pasted into the Cloud Account code field. Marketplace, org policy, provider sync and the worker proxy then go through one loop: assert server state, act in the UI, assert again. Evidence means health output, /tmp/den-*.log excerpts, CDP assertions and screenshots.
What it helps with
- stand up Den in a Daytona sandbox and aim a real Electron build at it
- verify the desktop app reads the sandbox
baseUrlinstead of production - prove cloud sign-in with a handoff code in Cloud Account
- attach a screen recording and screenshots to a pull request
- check that org policy survives a reload
Example prompts for the agent
- Start the Den server sandbox for
<branch-or-commit>and printDEN_WEB_URLandDEN_API_URL. - Run Electron against that Den sandbox with
--require-signinand save the recording asden-handoff. - Check that
baseUrlindesktop-bootstrap.jsonpoints at the sandbox and paste the health-check output.
How to install daytona-electron-den
1Skills CLI (Vercel)
npx skills add Devin-AXIS/iPolloWork --skill daytona-electron-den -a claude-code2Manually: put the files in place
~/.claude/skills/daytona-electron-den/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/daytona-electron-den/
1Skills CLI (Vercel)
npx skills add Devin-AXIS/iPolloWork --skill daytona-electron-den -a codex2Manually: put the files in place
.agents/skills/daytona-electron-den/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Devin-AXIS/iPolloWork --skill daytona-electron-den -a cursor2Manually: put the files in place
.cursor/skills/daytona-electron-den/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Devin-AXIS/iPolloWork .opencode/skills/daytona-electron-den2Manually: put the files in place
.github/skills/daytona-electron-den/SKILL.md1Skills CLI (Vercel)
npx skills add Devin-AXIS/iPolloWork --skill daytona-electron-den -a gemini-cli2Platform CLI
gemini skills install https://github.com/Devin-AXIS/iPolloWork --path .opencode/skills/daytona-electron-denManually: put the files in place
.devin/skills/daytona-electron-den/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-electron-den
How do I install daytona-electron-den in Claude Code?
Run npx skills add Devin-AXIS/iPolloWork --skill daytona-electron-den -a claude-code. The skill file then sits at ~/.claude/skills/daytona-electron-den/SKILL.md.
What does daytona-electron-den do?
It starts Den in one Daytona sandbox and launches Electron against it in a second, then compares what the server and the UI report. Cloud sign-in, marketplace, org policy and provider sync all get checked this way.
What do I need before running it?
Two Daytona sandboxes and the .devcontainer scripts that start the server and the Electron client. Both scripts take a branch or commit as their argument.