About nixos
An agent skill for resolving issues with an existing NixOS installation, using nix-pro and nixos MCP. It prohibits decrypting SOPS secrets.yaml and uses a marker file to prevent concurrent configuration builds or switches.
Key features
- 01Use nix-pro and nixos MCP for troubleshooting
- 02Never decrypt SOPS secrets.yaml
- 03Use research and code-reference tools as needed
- 04Create a marker file before builds or switches
- 05Wait for other NixOS jobs to finish building
Use cases
- 01Troubleshoot an existing NixOS installation
- 02Coordinate configuration builds and system switches
- 03Handle SOPS configuration under security constraints
MCP support
The skill directs agents to use nix-pro and nixos MCP to address issues with the current NixOS installation.
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/nixosin Claude Code to confirm it loaded.
Details
From the project READMEUse nix-pro and nixos MCP to resolve the following issues with the current NixOS installation.
-
Do not, under any circumstances, decrypt the SOPS secrets.yaml file. See the @CLAUDE.md file for extensive notes on this important security consideration.
-
Use Web Search and Perplexity as need for research and discovering resources.
-
Use sequential-thinking when appropriate to break down tasks further.
-
Use context7 whenever code examples might help.
-
Each time before you intend to build or switch to a new configuration, use
toucha create a file named/etc/nixos/.nixos-build. Remove this file when the build or the switch is completed. If you see that this file already exists, wait for up to ten minutes, checking every 10 seconds during that time to see if the file has been removed. This way, multiple nixos jobs can be working with the system at the same time, but only one will be building or switching at any given time.