ov-foundation/skills/arch-pac-test/SKILL.md
Test layer for pacman package installation on Arch Linux. Use when working with the arch-pac-test layer.
npx skillsauth add overthinkos/overthink-plugins arch-pac-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.
| Property | Value |
|----------|-------|
| Install files | layer.yml (packages only) |
| Depends | none |
PAC: neovim, ripgrep
Validates that the pac: package format works correctly on Arch Linux images. Installs neovim and ripgrep via pacman. Used as a smoke test for the multi-distro build system's Arch support.
# image.yml
layers:
- arch-pac-test
Requires an Arch-based image with build: [pac] (or [pac, aur]).
/ov-foundation:arch-test — Arch packaging test image/ov-foundation:arch-aur-test — companion AUR package testUse when the user asks about:
pac: package format in layer.ymlarch-pac-test layer/ov-build:layer — layer authoring reference (tasks, vars, env_provides, tests block syntax)/ov-build:eval — declarative testing framework for the eval: blocktools
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).