ov-foundation/skills/yay/SKILL.md
AUR helper for Arch Linux, enabling aur: package sections in layer.yml. Use when working with the yay layer 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 | layer.yml, tasks: |
| Depends | none |
PAC: base-devel, git
The tasks: task downloads the latest yay binary from GitHub releases:
# tasks: (in layer.yml)
tasks:
all:
cmds:
- |
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 layer.yml. Any layer with an aur: section requires a builder that has the yay layer (and builds: [aur] capability). The base-devel and git packages are prerequisites for building AUR packages.
# image.yml — typically in a builder image
layers:
- yay
Not used directly in end-user images. Instead, it's part of the builder image that compiles AUR packages during multi-stage builds.
/ov-foundation:archlinux-builder — Arch build infrastructure image/ov-coder:build-toolchain — C/C++ build tools (also in archlinux-builder)/ov-foundation:arch-aur-test — test layer that validates AUR buildsUse when the user asks about:
yay layer or AUR helper installationaur: packages in layer.yml get builtarchlinux-builder image's AUR capability/ov-build:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov-build:eval — declarative testing (eval: block, ov eval image, ov eval live)development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.