overthinkos/cloud-init
ov-layers/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.
devops
Updated Apr 24, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins cloud-initInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 2:40 PM193.5s1 file scanned
SKILL.md
- name:
- cloud-init
- description:
- |
cloud-init -- cloud instance initialization
Layer Properties
| Property | Value |
|----------|-------|
| Dependencies | sshd |
| Install files | tasks:, layer.yml |
Packages
cloud-init(RPM) -- cloud instance initializationcloud-utils-growpart(RPM) -- partition growing utility
Usage
# overthink.yml or image.yml
image:
my-cloud-image:
base: "quay.io/fedora/fedora-bootc:43"
bootc: true
layers:
- cloud-init
Used In Images
Used in bootc images for VM/cloud deployments. Depends on sshd.
Host-side pairing with kind: vm entities
This 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-dev: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-dev:cloud-init-rendereremitsuser-data+meta-data+network-config+ seeds ISO via xorriso.- This guest-side layer installs cloud-init so the guest reads
/dev/sr0(the seed ISO) at boot. - The
composeUsersadopt-merge pattern (renderer-side) deposits the SSH pubkey in~<base_user>/.ssh/authorized_keyswithoutuseradd.
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 vms.yml. For bootc VMs that want cloud-init provisioning, add this layer explicitly. See /ov-vms:vms for the authoring guide and /ov-vms:arch for a worked example.
Related Skills
/ov-layers:sshd-- SSH server dependency/ov-layers:bootc-base— composition that includes this layer/ov-layers:qemu-guest-agent— host-guest communication (paired with cloud-init in VMs)/ov:vm— VM lifecycle (create, start, stop, ssh) for kind:vm entities/ov-vms:vms— kind:vm authoring reference/ov-dev:cloud-init-renderer— host-side renderer producing the NoCloud seed ISO this layer reads/ov:layer— layer authoring reference
When to Use This Skill
Use when the user asks about:
- Cloud-init configuration or NoCloud datasource
- VM instance provisioning
- Cloud instance bootstrapping
- Partition growing with growpart
- System services: cloud-init-local, cloud-init, cloud-config, cloud-final
Related
/ov:test— declarative testing (tests:block,ov image test,ov test)
Related Skills
overthinkos/plugin
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jun 22, 2026
overthinkos/cue
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jun 16, 2026
overthinkos/egress
tools
VerifiedTrustedCommunity
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).
SKILL.mdUpdated Jun 16, 2026
overthinkos/check-k8s
tools
VerifiedTrustedCommunity
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).
SKILL.mdUpdated Jun 14, 2026