tools/skills/yay/SKILL.md
AUR helper for Arch Linux, enabling aur: package sections in charly.yml. Use when working with the yay candy or Arch AUR builds.
npx skillsauth add overthinkos/overthink-plugins yayInstall 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 | charly.yml (run: step) |
| Depends | none |
PAC: base-devel, git
The run: step downloads the latest yay binary from GitHub releases:
# yay charly.yml — a plan step is a child step node (no plan: list)
yay:
candy:
version: 2026.144.1443
yay-step-0:
run: download the latest yay binary from GitHub releases
command: |
ARCH=$(uname -m)
URL=$(curl -fsSL https://api.github.com/repos/Jguer/yay/releases/latest \
| grep -o "https://github.com/Jguer/yay/releases/download/[^\"]*_${ARCH}.tar.gz")
curl -fsSL "$URL" | tar -xzf - -C /usr/local/bin --strip-components=1 --wildcards '*/yay'
Architecture-aware: downloads the correct binary for x86_64 or aarch64.
Installs the yay AUR helper, which enables the aur: package format in charly.yml. Any candy with an aur: section requires a builder that has the yay candy (and builds: [aur] capability). The base-devel and git packages are prerequisites for building AUR packages.
# charly.yml — typically in a builder image (name-first; compose via a child node)
my-builder:
candy:
base: arch
my-builder-candy:
candy:
- yay
Not used directly in end-user boxes. Instead, it's part of the builder image that compiles AUR packages during multi-stage builds.
/charly-distros:arch-builder — Arch build infrastructure image/charly-coder:build-toolchain — C/C++ build tools (also in arch-builder)/charly-distros:arch-aur-test — test candy that validates AUR buildsUse when the user asks about:
yay candy or AUR helper installationaur: packages in charly.yml get builtarch-builder box's AUR capability/charly-image:layer — candy authoring reference (charly.yml schema, plan-step verbs, service declarations)/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).