crabbox
Detect and use Crabbox for repository tests and validation on remote runners. Use when crabbox.yaml or .crabbox.yaml exists, the crabbox CLI is available, or work needs remote compute, a clean or reusable environment, target-platform coverage, or auditable execution evidence.
Profile →npx skills add openclaw/crabbox --skill crabbox --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Crabbox Use Crabbox when a project needs remote proof, larger cloud capacity, a fresh PR checkout, a reusable warmed box, GitHub Actions-style setup, durable run logs/results, UI proof artifacts, or sync from a dirty local checkout. ## Detect Crabbox - Treat repo-root `crabbox.yaml` or `.crabbox.yaml` as an intentional signal to use this skill for validation work. `.crabbox.yml` is not a supported config filename. - If neither config exists, `command -v crabbox` still identifies an installed CLI. Run `crabbox doctor` before depending on it for remote work. - Inspect config before executing it. Detection does not imply permission to expose secrets, bypass command approval, or start paid infrastructure. ## Source Of Truth - Run Crabbox from the repository root; sync mirrors the current checkout. - Treat repo-local `crabbox.yaml` or `.crabbox.yaml` as executable project automation. Review it before remote runs, especially `provider`, `actions`, `jobs`, `profiles`, `env.allow`, artifacts, and cleanup policy. - Verify the installed binary before relying on examples: `command -v crabbox && crabbox --version && crabbox --help | sed -n '1,120p'`. - Use `crabbox providers` or `crabbox pro
- Detect Crabbox
- Source Of Truth
- Auth And Config
- Choose The Remote Surface
- Common Remote Proof
- Sync And Fresh Checkouts
- Scripts, Shells, And Windows Targets
- Hyper-V Windows leases
- Secrets And Environment Forwarding
- Profiles, Presets, Proof, And Results
- Run Handles And Observability
- Desktop, WebVNC, And UI Proof
- Provider Boundaries
- Local And Static Targets
crabbox login --url <broker-url> crabbox whoami crabbox doctor printf '%s' "$CRABBOX_COORDINATOR_TOKEN" | crabbox login --url <broker-url> --provider aws --token-stdin crabbox run --preflight --timing-json -- pnpm test crabbox warmup --class beast --idle-timeout 90m crabbox status --id <cbx_id-or-slug> --wait crabbox run --id <cbx_id-or-slug> -- pnpm test:changed crabbox run --id <cbx_id-or-slug> --full-resync -- pnpm test:changed
What does the crabbox skill do?
Detect and use Crabbox for repository tests and validation on remote runners. Use when crabbox.yaml or .crabbox.yaml exists, the crabbox CLI is available, or work needs remote compute, a clean or reusable environment, target-platform coverage, or auditable execution evidence.
How do I install it?
Run `npx skills add openclaw/crabbox --skill crabbox --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From openclaw/crabbox, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.