agentleFS
olafkfreundolafkfreund/nix-skills/skills/nixos-operations/SKILL.md

nixos-operations

Skill9 starsChanged 55 days agoMITView on GitHub

Operate NixOS systems by choosing rebuild modes, managing generations and rollback, upgrading, cleaning the store, and diagnosing boot and service problems.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the repository instructions and find out how the system is built:

    line 10
  2. Very specific:

    Start with build or dry-activate to validate a change.

    line 37
  3. Very specific:

    Use home-manager for user environments, nixpkgs-development for packaging, nixos-wiki for community guidance, and nix-workflow for general …

    line 63
  4. Very specific:

    Never search /nix/store (for example find /nix/store/*foo-* -name libfoo.so) and never copy a literal store path.

    line 73
  5. Very specific:

    Do not quote attribute names that are valid identifiers ([A-Za-z_][A-Za-z0-9_'-]*, dashes included).

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

NixOS operations

Establish the setup first

Read the repository instructions and find out how the system is built:

  • a flake with nixosConfigurations.<host>, or channels with /etc/nixos/configuration.nix;
  • the NixOS release (nixos-version) and system.stateVersion;
  • the host being changed.

The bundled operations reference quotes the NixOS manual at the Nixpkgs master snapshot in sources.json, not necessarily the user's release. Check version-sensitive behaviour against the user's release. Never treat the manual's examples as a reason to move a system between channels and flakes.

Rebuild modes

nixos-rebuild builds a configuration and optionally activates it. Add --flake .#HOST for flake systems.

ModeEffectChanges the running system
dry-buildShow what would be built or fetchedNo
buildBuild into ./resultNo
dry-activateBuild and show what activation would changeNo
testActivate now, but keep the previous boot defaultYes
bootMake it the boot default, activating on next bootYes, at reboot
switchActivate now and make it the boot defaultYes

Start with build or dry-activate to validate a change. test, boot, switch, --rollback, --upgrade and --target-host deployments change a system. Propose them with the exact command, and run them only with the user's authorization. The same applies to restarting services, deleting generations, collecting garbage and changing boot entries.

Generations, rollback and upgrades

nixos-rebuild list-generations lists system generations. For rollback and boot-menu recovery, read Rolling Back Configuration Changes. For channel upgrades and flake input updates, read Upgrading NixOS. Treat an upgrade as a deliberate, reviewable change: update inputs separately from configuration edits, and build before switching.

Store cleaning, boot and services

  • Cleaning the Nix Store explains garbage collection, and how deleting old generations removes rollback targets. Confirm which generations the user still needs first.
  • Boot Problems covers kernel parameters and emergency shells.
  • Service Management covers systemctl and journalctl. Reading status and logs is safe. Starting, stopping, restarting and enabling services change the system.

Related skills

Use home-manager for user environments, nixpkgs-development for packaging, nixos-wiki for community guidance, and nix-workflow for general Nix command-line practice, if they are installed. Otherwise use the NixOS manual.

Modified excerpts from the Nixpkgs contributors are covered by COPYING.

Nix style

  • Never search /nix/store (for example find /nix/store/*foo-* -name libfoo.so) and never copy a literal store path. Find the providing package with nix-locate, and refer to it through Nix: ${pkgs.foo}/lib or lib.makeLibraryPath [ pkgs.foo ].
  • Do not quote attribute names that are valid identifiers ([A-Za-z_][A-Za-z0-9_'-]*, dashes included). Write pkgs.foo-bar and packages.x86_64-linux, not pkgs."foo-bar". Quote only other names (".config/foo", "2.0"), the keywords assert else if in inherit let or rec then with, and interpolations ("${name}"). Upstream examples in references sometimes quote needlessly; do not copy that style.

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.