distros/skills/bootc-base/SKILL.md
Base composition for bootc OS images including SSH, QEMU guest agent, and bootc config. Use when working with bootable container images, VMs, or OS-level configuration.
npx skillsauth add overthinkos/overthink-plugins bootc-baseInstall 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 |
|----------|-------|
| Layers (composition) | sshd, qemu-guest-agent, bootc-config |
| Install files | none (pure composition) |
# box.yml
my-os:
layers:
- bootc-base
/charly-coder:sshd -- SSH server (included)/charly-distros:qemu-guest-agent -- QEMU guest agent (included)/charly-distros:bootc-config -- bootc system configuration (included)/charly-tools:charly -- often paired for the full VM toolchain (charly binary + virtualization + gocryptfs + socat)Use when the user asks about:
/charly-image:layer — layer authoring reference (candy.yml schema, task verbs, service declarations)/charly-eval:eval — declarative testing (eval: block, charly eval box, charly eval 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).