ov-images/skills/arch-test/SKILL.md
Test image for Arch Linux pacman and AUR package installation. MUST be invoked before building or troubleshooting the arch-test image.
npx skillsauth add overthinkos/overthink-plugins arch-testInstall 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.
Test image that validates both pac: (pacman) and aur: (AUR) package formats on Arch Linux. Used to verify the multi-distro build system handles Arch packaging correctly.
| Property | Value | |----------|-------| | Base | archlinux | | Build | pac, aur | | Layers | agent-forwarding, arch-pac-test, arch-aur-test | | Platforms | linux/amd64 | | Registry | ghcr.io/overthinkos |
pac: format (via arch-pac-test) — installs neovim and ripgrep from official Arch reposaur: format (via arch-aur-test) — installs yay-bin from the AUR using archlinux-builderov image build arch-test
ov shell arch-test
ov shell arch-test -c "nvim --version" # pac: package installed
ov shell arch-test -c "rg --version" # pac: package installed
ov shell arch-test -c "which yay" # aur: package installed
/ov-images:archlinux — base image/ov-images:archlinux-builder — builder image (provides yay for AUR builds)/ov-layers:arch-pac-test — pacman test layer/ov-layers:arch-aur-test — AUR test layerMUST be invoked when the task involves building or troubleshooting the arch-test image, or validating Arch Linux package format support.
/ov:image — image family umbrella (image: entries in overthink.yml, build/validate/inspect/list)/ov:build — build.yml vocabulary (distros, builders, init-systems)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).