local/skills/ov-cachyos/SKILL.md
Operator CachyOS workstation profile — a kind:local template + target:local deploy that installs the full dev stack (30 layers) onto a CachyOS host via ShellExecutor. Lives in the overthinkos/cachyos submodule. MUST be invoked before editing or applying the ov-cachyos workstation profile.
npx skillsauth add overthinkos/overthink-plugins ov-cachyosInstall 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.
The operator's CachyOS developer-workstation profile: a kind: local template
(local.ov-cachyos) plus a target: local + host: local deploy entry
(deploy.ov-cachyos) that applies a kitchen-sink dev stack directly to the
current machine via ShellExecutor — no SSH, no VM, no container.
It lives in the overthinkos/cachyos repo (git submodule at
image/cachyos), inlined in that repo's single overthink.yml — both the
kind: local template and the kind: deploy entry (the lone kind: deploy in
that repo; every disposable test bed there is kind: eval). Apply it with:
ov -C image/cachyos update ov-cachyos
# or, anywhere:
ov --repo overthinkos/cachyos update ov-cachyos
30 layers. Most are pulled from the main repo by git reference
(@github.com/overthinkos/overthink/layers/<name>:<tag>); the cachyos-exclusive
ghostty, keepassxc-keyring, and wheel-nopasswd are vendored locally in this
repo's layers/ (resolved via its discover: block):
wheel-nopasswd, yay, dev-tools, gh, pre-commit, tmux, direnv,
gnupg, keepassxc, keepassxc-keyring, tailscale, tailscale-up,
build-toolchain, golang, rust, nodejs, uv, claude-code, codex,
gemini, oracle, forgecode, devops-tools, docker-ce, kubernetes,
vscode, ghostty, chrome, nvidia, ov-full.
| Field | Value |
|---|---|
| install_opts.builder_image | ghcr.io/overthinkos/arch-builder:2026.122.2252 (OCI ref, not a layer) |
| install_opts | with_service, allow_repo_changes, allow_root_tasks all true |
| env | EDITOR=nvim, PAGER=less |
| disposable (deploy) | true — ov update ov-cachyos is authorized |
passwordless-sudo-host — sudo -n true (wheel-nopasswd layer must have run)nvidia-ctk-present — command -v nvidia-ctknvidia-cdi-spec — /etc/cdi/nvidia.yaml existslocal.ov-cachyos's remote layer refs are collected and materialized by the
same CollectRemoteRefs walk as image layer refs: the walk collects the layer
refs of the ROOT project's own kind: local templates (ov-cachyos is the root
here), so ov image validate / ov update ov-cachyos resolve the github-ref'd
layers. (Collection is reachability-scoped — a namespace's kind:local
templates, imported only as a dependency, are NOT collected by an importer; only
the root's own locals are. See /ov-internals:go "Remote-layer resolver".)
/ov-local:local-spec — kind: local template authoring reference/ov-local:local-deploy — the target: local deployment surface/ov-distros:cachyos — the CachyOS base of the same family/ov-core:deploy — deploy entry semantics (cross-kind name reuse: deploy.ov-cachyos ↔ local.ov-cachyos)MUST be invoked when editing or applying the ov-cachyos workstation profile, or reasoning about the kind:local remote-layer-ref machinery. Invoke BEFORE reading source code or launching Explore agents.
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.