Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
.claude/skills/devin-axis-daytona-cloud-server/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | -23% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -56% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -50% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -72% | 0% |
| case-08 | ✗→✓ | ▲ Improved | -69% | 0% |
Use this skill when the user needs the hosted/server side of iPolloWork running in Daytona. This is separate from the Electron desktop sandbox.
3005.8788.8789.From the repo root:
bashbash .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:
bashbash .devcontainer/create-daytona-ipollowork-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:
bashbash .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:
bashcurl -sf <DEN_WEB_URL>/api/den/health curl -sf <DEN_API_URL>/health
Inspect logs if health checks fail:
bashdaytona 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 fraimz for pass/fail. Server health alone does not prove Electron cloud behavior works.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 15,054 | 15,141 | +1% | 1 | 1 | 0% | 219 | 1,055 | +382% | 0 | 0 | — |
case-02 | fail→fail | 23,581 | 15,263 | -35% | 1 | 1 | 0% | 1,628 | 1,050 | -36% | 0 | 0 | — |
case-03 | fail→fail | 13,367 | 8,316 | -38% | 1 | 1 | 0% | 1,450 | 1,128 | -22% | 0 | 0 | — |
case-04 | fail→pass | 13,188 | 7,001 | -47% | 1 | 1 | 0% | 1,275 | 980 | -23% | 0 | 0 | — |
case-05 | fail→pass | 16,924 | 6,445 | -62% | 1 | 1 | 0% | 2,066 | 900 | -56% | 0 | 0 | — |
case-06 | fail→pass | 16,422 | 6,394 | -61% | 1 | 1 | 0% | 1,808 | 896 | -50% | 0 | 0 | — |
case-07 | fail→pass | 24,983 | 6,658 | -73% | 1 | 1 | 0% | 3,166 | 883 | -72% | 0 | 0 | — |
case-08 | fail→pass | 24,079 | 6,809 | -72% | 1 | 1 | 0% | 3,000 | 938 | -69% | 0 | 0 | — |
case-09 | pass→pass | 16,933 | 6,896 | -59% | 1 | 1 | 0% | 1,787 | 1,013 | -43% | 0 | 0 | — |
case-10 | fail→pass | 30,467 | 7,269 | -76% | 1 | 1 | 0% | 4,314 | 1,051 | -76% | 0 | 0 | — |
case-11 | fail→pass | 17,132 | 7,336 | -57% | 1 | 1 | 0% | 1,899 | 1,005 | -47% | 0 | 0 | — |
case-12 | fail→pass | 13,810 | 7,155 | -48% | 1 | 1 | 0% | 1,438 | 1,036 | -28% | 0 | 0 | — |
case-13 | fail→pass | 16,545 | 6,310 | -62% | 1 | 1 | 0% | 1,700 | 838 | -51% | 0 | 0 | — |
case-14 | pass→pass | 19,833 | 15,245 | -23% | 1 | 1 | 0% | 2,236 | 2,181 | -2% | 0 | 0 | — |
case-15 | fail→pass | 16,273 | 8,762 | -46% | 1 | 1 | 0% | 2,149 | 1,393 | -35% | 0 | 0 | — |
case-16 | pass→pass | 18,911 | 6,990 | -63% | 1 | 1 | 0% | 2,383 | 1,013 | -57% | 0 | 0 | — |
case-17 | fail→pass | 16,645 | 7,557 | -55% | 1 | 1 | 0% | 1,921 | 1,090 | -43% | 0 | 0 | — |
case-18 | fail→pass | 15,072 | 6,396 | -58% | 1 | 1 | 0% | 1,570 | 860 | -45% | 0 | 0 | — |
case-19 | pass→pass | 12,940 | 7,456 | -42% | 1 | 1 | 0% | 1,169 | 1,030 | -12% | 0 | 0 | — |
case-20 | fail→pass | 17,705 | 12,113 | -32% | 1 | 1 | 0% | 2,180 | 1,923 | -12% | 0 | 0 | — |
case-21 | fail→fail | 22,118 | 15,017 | -32% | 1 | 1 | 0% | 3,033 | 2,545 | -16% | 0 | 0 | — |
case-22 | fail→fail | 21,623 | 18,854 | -13% | 1 | 1 | 0% | 3,173 | 3,223 | +2% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 20 counted toward the lift figure. The other 2 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +59 percentage points is the difference between those two pass rates over the 20 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.