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 | run: steps, charly.yml |
cloud-init (RPM) -- cloud instance initializationcloud-utils-growpart (RPM) -- partition growing utility# charly.yml
my-cloud-image:
candy:
base: "quay.io/fedora/fedora-bootc:43"
bootc: true
my-cloud-image-candy:
candy:
- cloud-init
Used in bootc images for VM/cloud deployments. Depends on sshd.
kind: vm entitiesThis candy 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 charly binary itself (/charly-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:
/charly-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 candy isn't needed; author the VM entity directly in vm.yml. For bootc VMs that want cloud-init provisioning, add this candy explicitly. See /charly-vm:vms-catalog for the authoring guide and /charly-vm:arch for a worked example.
/charly-coder:sshd -- SSH server dependency/charly-distros:qemu-guest-agent — host-guest communication (paired with cloud-init in VMs)/charly-vm:vm — VM lifecycle (create, start, stop, ssh) for kind:vm entities/charly-vm:vms-catalog — kind:vm authoring reference/charly-internals:cloud-init-renderer — host-side renderer producing the NoCloud seed ISO this candy reads/charly-image:layer — candy authoring referenceUse when the user asks about:
/charly-check:check — declarative testing (check: block, charly check box, charly check live)tools
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
tools
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
tools
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
tools
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).