agentleFS
Sign inStart free
Lukk17Lukk17/agent-standards/.agents/skills/cachyos/SKILL.md

cachyos

Skill1 starsChanged 8 days agoMITView on GitHub

CachyOS administration on top of Arch: linux-cachyos kernels, the x86-64-v3 and v4 repositories, chwd and NVIDIA modules, sched-ext schedulers, cachyos-settings, and Limine with snapshot boot entries. Use when the user says "switch to the bore kernel", "should I use the v4 repos", "black screen after the nvidia update" or "the system will not boot". Not for generic pacman work, use `arch-linux`.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never edit shipped files under /usr/lib or /usr/share.

    line 53
  2. Very specific:

    Keep the CachyOS repositories above [core] in pacman.conf, and never replace the file with its .pacnew.

    line 54
  3. Very specific:

    Never add nvidia-dkms, nvidia-open-dkms or another driver set by hand on top of a prebuilt linux-cachyos*-nvidia* module package.

    line 55
  4. Distinctive:

    Keep a second known good kernel installed and bootable at all times.

    line 56
  5. Distinctive:

    Do not add third party pacman repositories, including ones that offer agent skill packages.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CachyOS Administration

CachyOS is a rolling Arch derivative with its own kernels, repositories rebuilt for newer CPU instruction sets, a tuned settings package and its own tools. The Arch Wiki is still the background, but where it and CachyOS differ, what the CachyOS packages ship on the machine wins. Read the arch-linux skill as well, because every generic package, snapshot and journal rule applies here unchanged.

Written for CachyOS with Limine and snapper. The commands that ran were run on one host, and commands that were not executed are marked UNVERIFIED in the topic files.

You are about toOpen
Edit /etc/pacman.conf, add or change a CachyOS repository, rank mirrors, consider v4 or znver4repos-v3.md
Install, switch, remove or upgrade a kernel, use kerverkernel.md
Touch the NVIDIA driver, run chwd, change the GPU, fix a black screen after an upgradehardware-nvidia.md
Change the scheduler, scx_loader, ananicy-cpp, the power profile, sysctl, zram, the I/O schedulerperformance.md
Touch the bootloader, the kernel command line, snapshot boot entries, recover from a live ISOboot-limine.md
Change something a cachyos-*-settings package owns, the login manager, /etc/skeldesktop-defaults.md

Machine facts

Machine-specific facts live in MACHINE.md next to the global AGENTS.md: the CPU and its ISA level, the GPU and driver packaging, installed kernels, the bootloader and its command line, disks that must never be touched, and the change log. Read it before acting. This skill holds no facts about any single machine. Discover them with the commands in the topic files and compare with MACHINE.md.

When to activate

  • A question about a linux-cachyos* kernel, its modules or its headers
  • An edit to /etc/pacman.conf or a CachyOS mirrorlist
  • chwd, a GPU driver change, or a display that broke after an upgrade
  • scx_loader, ananicy-cpp, power-profiles-daemon, zram or a sysctl from cachyos-settings
  • Limine, /etc/default/limine, snapshot boot entries, or a machine that does not boot
  • cachyos-kde-settings, /etc/skel, or the login manager
  • Also covers linux-cachyos kernel flavors and switching, kerver, cachyos-kernel-manager, the x86-64-v3 and v4 optimized repositories and pacman.conf order, cachyos-mirrorlist and cachyos-rate-mirrors, chwd hardware profiles, the prebuilt NVIDIA module packages, scx_loader and sched-ext, ananicy-cpp, power-profiles-daemon, game-performance, zram and cachyos-settings, the Limine bootloader with limine-snapper-sync and limine-mkinitcpio, snapshot boot entries, cachy-chroot recovery, cachyos-kde-settings and the login manager
  • The user says "chwd", "enable scx_lavd", "change the kernel command line" or "restore a snapshot from the boot menu"

When not to activate

  • Generic pacman, AUR, .pacnew, cleanup, snapper, journal, crash or audio work, use arch-linux
  • Plasma panels, widgets, KWin, shortcuts, themes or konsave, use kde-plasma
  • Provisioning a CachyOS host reproducibly, use ansible

Hard rules

  1. This is not vanilla Arch. Check what a CachyOS package owns with pacman -Qo before applying an Arch Wiki recipe.
  2. Never edit shipped files under /usr/lib or /usr/share. Override in /etc or ~, as the arch-linux skill describes.
  3. Keep the CachyOS repositories above [core] in pacman.conf, and never replace the file with its .pacnew.
  4. Never add nvidia-dkms, nvidia-open-dkms or another driver set by hand on top of a prebuilt linux-cachyos*-nvidia* module package.
  5. Keep a second known good kernel installed and bootable at all times.
  6. Do not add third party pacman repositories, including ones that offer agent skill packages.
  7. The agent does not run sudo, and every root step goes to the owner with what it changes.

Related skills

  • arch-linux owns pacman, the AUR, snapshots, the journal, crash diagnosis, audio and safe configuration
  • kde-plasma owns the Plasma desktop that cachyos-kde-settings seeds
  • ansible owns provisioning the same state reproducibly

Checklist

  • MACHINE.md read, and the CPU ISA level, GPU, kernels and bootloader discovered or confirmed
  • A snapshot taken before any kernel, driver, bootloader or initramfs change
  • Kernel, headers and module package installed or removed as one flavor set
  • A fallback kernel still installed and listed in the boot menu
  • No hand-installed DKMS driver on top of a prebuilt module
  • Boot options changed in /etc/default/limine, never in the generated limine.conf
  • The change and its undo recorded in the MACHINE.md change log

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free