Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
Install
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Devin-AXIS/iPolloWork --skill daytona-cloud-server -a cursor -y
Download .opencode/skills/daytona-cloud-server/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does daytona-cloud-server live?
The publisher keeps it at https://github.com/Devin-AXIS/iPolloWork.
Which agents can use daytona-cloud-server?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
name: daytona-cloud-server
description: Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
Daytona Cloud Server
Use this skill when the user needs the hosted/server side of iPolloWork running in
Daytona. This is separate from the Electron desktop sandbox.
What This Covers
Den Web on port 3005.
Den API on port 8788.
Worker proxy on port 8789.
MySQL inside the server sandbox.
Public Daytona preview URLs for Electron to consume.
Marketplace, org policy, cloud auth, and server-managed extension flows.
For end-to-end desktop validation, use the daytona-electron-den skill. This
section only covers wiring the Electron sandbox to the printed server URLs.
Start a second Daytona sandbox for Electron and point it at the server URLs:
Use two sandboxes when testing cloud behavior end-to-end: server sandbox for Den
and a separate Electron sandbox for the desktop client. This matches production
better than trying to run everything inside one desktop sandbox.
Use this for marketplace install/remove/search/filter, org-managed extensions,
desktop handoff auth, cloud restrictions, and worker proxy flows.
Evidence
Pair this with the daytona-recording-artifacts skill. Server proof should
include health-check output, relevant logs, CDP assertions from Electron, and a
recording or screenshot artifact for human review.
Use fraimz for pass/fail. Server health alone does not prove
Electron cloud behavior works.
How do I install daytona-cloud-server?
Download .opencode/skills/daytona-cloud-server/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does daytona-cloud-server live?
The publisher keeps it at https://github.com/Devin-AXIS/iPolloWork.
Which agents can use daytona-cloud-server?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.