Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ai-builder-club/crabbox-setup
Scaffold an isolated CLOUD dev box per agent (via crabbox + Daytona) for any codebase — the parallel-safe counterpart to dev-local-setup. Each agent gets its own full stack (own DB + dev server) and an in-box browser for e2e, so concurrent loops never collide on ports/state. Sets up the snapshot image, .crabbox.yaml, an idempotent setup.sh (also boots the stack locally), and a cbx.sh wrapper.
Passed 16 of 19 test cases with the skill, and 3 of 19 without it.
and 23 more in the full report
15 fixed3 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are ready to build the remote box image snapshot on Daytona using our `devbox/Dockerfile`. What is the exact CLI command to build this snapshot with 4 CPUs, 8GB RAM, and 10GB disk in the US region?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the command daytona snapshot create with --dockerfile devbox/Dockerfile and --context devbox. | Missed | Passed |
| Includes --cpu 4, --memory 8, --disk 10, and --region us flags in the snapshot creation command. | Missed | Passed |
The instructions your model reads when the skill loads.
dev-local-setup gives you one local stack. But the loop-engineer model runs
many loops in parallel, and you can't run N full stacks on one laptop — fixed
ports, one Docker daemon, one shared DB; worktrees don't fix that (they still share
the host). This skill is the cloud/parallel counterpart: a fresh isolated box per
agent (own DB + dev server), driven by an in-box browser, so concurrent code
loops verify their work without colliding — laptop at ~0% CPU.
Written for Daytona (snapshot-based, the proven path); notes for SSH-lease providers (Hetzner/AWS) at the end. It composes with the rest of the harness:
dev-local-setup's service/port discovery — don't re-discover.e2e-setup specs on the box as the verification.You are SCAFFOLDING files into the target repo. Templates live in assets/ (next to
this skill); copy them in and ADAPT (every one has # EDIT: markers).
If scripts/dev-local.sh exists, read it: it already encodes the services, ports,
infra deps, and start commands. The box's setup.sh should mirror it so local and
cloud stay in sync. Otherwise discover the same facts (package manager, dev cmd +
port, backing services, secrets) — see dev-local-setup Step 1. Decide:
env.allow (Step 3), never sync.devbox/DockerfileCopy assets/Dockerfile → devbox/Dockerfile; adapt. It bakes the slow STATIC tools
(NOT app code — crabbox syncs that at run time, so the build context is just devbox/).
docker:dind — docker 28+ defaults to the
containerd overlayfs snapshotter, which Daytona's kernel rejects (overlay mount … no such file or directory). 27.x keeps the working overlay2 graphdriver.chrome channel playwright-cli uses
— NOT chromium), @playwright/cli, and playwright's bundled ffmpeg (for video).daytona login first)test cases passed, vs 3 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.