メニュー
Daytona cloud server and Den sandbox setup. Use when the user says Daytona server, cloud server, Den server, marketplace server, worker proxy, cloud auth, org policies, or connect Electron to a Daytona server.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/TashanGKD/tashanwork --skill daytona-cloud-serverコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Daytona cloud instance, Den server, OpenWork Cloud, Marketplace onboarding. Use when the user asks to run, launch, start, validate, or record a Daytona cloud/Den instance for OpenWork Cloud flows.
Validate Electron against a Daytona Den server. Use for two-sandbox cloud auth, marketplace, org policy, worker proxy, provider sync, or desktop handoff flows.
Daytona Electron sandbox testing with CDP/noVNC. Use when the user says test on Daytona, run Electron on Daytona, Daytona dry run, test Electron remotely, reproduce on Daytona, or validate a real desktop flow.
| name | daytona-cloud-server |
| description | Daytona cloud server and Den sandbox setup. Use when the user says Daytona server, cloud server, Den server, marketplace server, worker proxy, cloud auth, org policies, or connect Electron to a Daytona server. |
Use this skill when the user needs the hosted/server side of OpenWork running in Daytona. This is separate from the Electron desktop sandbox.
3005.8788.8789.From the repo root:
bash .devcontainer/test-server-on-daytona.sh [branch-or-commit]
The helper creates a separate server sandbox, starts MySQL, Den API, Den Web, and worker proxy, waits for health checks, then prints URLs.
If dependencies or the base image changed, refresh the server snapshot:
bash .devcontainer/create-daytona-openwork-server-snapshot.sh
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:
bash .devcontainer/test-on-daytona.sh [branch-or-commit] \
--den-base-url <DEN_WEB_URL> \
--den-api-base-url <DEN_API_URL>
For flows that must require cloud sign-in, add --require-signin.
Use the public URLs printed by the helper:
curl -sf <DEN_WEB_URL>/api/den/health
curl -sf <DEN_API_URL>/health
Inspect logs if health checks fail:
daytona exec "$SERVER_SANDBOX" -- 'tail -120 /tmp/den-api.log'
daytona exec "$SERVER_SANDBOX" -- 'tail -120 /tmp/den-web.log'
daytona exec "$SERVER_SANDBOX" -- 'tail -120 /tmp/den-worker-proxy.log'
daytona exec "$SERVER_SANDBOX" -- 'tail -120 /tmp/den-db-push.log'
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.
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 daytona-flow-validator for pass/fail. Server health alone does not prove
Electron cloud behavior works.