Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Devin-AXIS/iPolloWork --skill daytona-electron-den -a claude-code
Open on GitHub

What 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 baseUrl instead 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 print DEN_WEB_URL and DEN_API_URL.
  • Run Electron against that Den sandbox with --require-signin and save the recording as den-handoff.
  • Check that baseUrl in desktop-bootstrap.json points 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-code

2Manually: put the files in place

~/.claude/skills/daytona-electron-den/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/daytona-electron-den/

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.

Similar skills

All skills for Testing and QA →

From the same set42

The whole set →
get-env-var get-env-var is a Claude Code skill that loads Infisical secrets into the shell environment or runs a command with project secrets. It lets scripts access a token or API key. CX Codex +1 ★ 7,523repo stars daytona-chrome-cdp daytona-chrome-cdp starts a separate Chromium inside a Daytona sandbox and exposes it over CDP, so you can finish web sign-in, OAuth or admin flows in a real browser. CX Codex +1 ★ 7,523repo stars ipollowork-presentations ipollowork-presentations guides agents in building and refining slide decks inside an iPolloWork Design session while keeping layout contracts and tokens intact. CX Codex +1 ★ 7,523repo stars daytona-cloud-server daytona-cloud-server starts iPolloWork’s server side in Daytona, including Den, MySQL, and the worker proxy. Use it to test cloud flows separately from the Electron client. CX Codex +1 ★ 7,523repo stars fraimz Runs end-to-end evaluation flows for an Electron app and generates step-by-step visual proof in fraimz.html with screenshots. CX Codex +1 ★ 7,523repo stars run-evals The run-evals skill launches iPolloWork and runs coded E2E flows through CDP. Use it to check a feature and produce run artifacts for a PR. CX Codex +1 ★ 7,523repo stars voiceover The voiceover skill writes the demo narration before any code exists, then carries the feature through to a pull request with frame-by-frame proof attached. Useful when the team should agree on what a viewer sees first. CX Codex +1 ★ 7,523repo stars image-generation image-generation generates image assets through the iPolloWork service for slide decks and web pages. Operates directly in chat without opening Image Studio. CX Codex +1 ★ 7,523repo stars

Project sponsors

Companies that keep this analytics open