What problem does it solve?
Managing Cloud Worker images across multiple providers (AWS, Hetzner, Firecracker) is error-prone, with risks of leaking secrets, breaking config, or losing track of superseded snapshots. This Skill enforces a disciplined gather-mutate-repair-prove-report workflow so image bakes are reproducible and safe.
Core Features & Use Cases
- Multi-provider image baking: Lease workers via crabbox, install tooling, and snapshot through AWS native, Hetzner hcloud, or Firecracker rootfs pipelines.
- Validated config updates: Point profiles at new images only through
openclaw config schema-checked writes, never hand-edited files.
- Proof-driven promotion: Verify baked tooling with timed warmups and end-to-end session dispatch before retiring the previous image.
- Use Case: Rolling out a new Node.js runtime on AWS Cloud Workers by leasing, installing, snapshotting, promoting, and dispatching a test session before deleting the old AMI.
Quick Start
Use the cloud-image-bake skill to bake a new AWS Cloud Worker image with the latest Node.js runtime, prove it via a timed warmup, and report the rollback state.