distros/skills/cloud-init/SKILL.md
Cloud-init for instance initialization in cloud/VM environments with NoCloud datasource. Use when working with cloud-init, VM provisioning, or cloud instance bootstrapping.
npx skillsauth add overthinkos/overthink-plugins cloud-initInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Dependencies | sshd |
| Install files | task:, layer.yml |
cloud-init (RPM) -- cloud instance initializationcloud-utils-growpart (RPM) -- partition growing utility# overthink.yml or image.yml
image:
my-cloud-image:
base: "quay.io/fedora/fedora-bootc:43"
bootc: true
layers:
- cloud-init
Used in bootc images for VM/cloud deployments. Depends on sshd.
kind: vm entitiesThis layer installs the guest-side cloud-init package — the daemon that reads a NoCloud seed ISO at first boot. The host-side companion is the RenderCloudInit path in the ov binary itself (/ov-internals:cloud-init-renderer), which produces that seed ISO from the structured VmSpec.CloudInit block on a kind: vm entity.
The two sides cooperate across the host/guest boundary:
/ov-internals:cloud-init-renderer emits user-data + meta-data + network-config + seeds ISO via xorriso./dev/sr0 (the seed ISO) at boot.composeUsers adopt-merge pattern (renderer-side) deposits the SSH pubkey in ~<base_user>/.ssh/authorized_keys without useradd.For cloud_image VMs (source.kind: cloud_image), cloud-init typically comes pre-installed in the upstream qcow2 — this layer isn't needed; author the VM entity directly in vm.yml. For bootc VMs that want cloud-init provisioning, add this layer explicitly. See /ov-vm:vms-catalog for the authoring guide and /ov-vm:arch for a worked example.
/ov-coder:sshd -- SSH server dependency/ov-distros:bootc-base — composition that includes this layer/ov-distros:qemu-guest-agent — host-guest communication (paired with cloud-init in VMs)/ov-vm:vm — VM lifecycle (create, start, stop, ssh) for kind:vm entities/ov-vm:vms-catalog — kind:vm authoring reference/ov-internals:cloud-init-renderer — host-side renderer producing the NoCloud seed ISO this layer reads/ov-image:layer — layer authoring referenceUse when the user asks about:
/ov-eval:eval — declarative testing (eval: block, ov eval image, ov eval live)development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.