nixos
Resolve NixOS issues using research and sequential thinking
When & Why to Use This Skill
This Claude skill is a specialized automation tool for managing and troubleshooting NixOS environments. It leverages sequential thinking and integrated research tools like Perplexity to diagnose complex configuration issues, manage system builds with built-in concurrency protection, and provide code-verified solutions while maintaining strict security standards for encrypted secrets.
Use Cases
- NixOS Configuration Troubleshooting: Automatically identifying and resolving syntax or logic errors in NixOS configuration files through deep research and sequential reasoning.
- Safe System Build Management: Utilizing a file-locking mechanism (/etc/nixos/.nixos-build) to prevent conflicts during concurrent system builds or environment switches.
- Technical Resource Discovery: Using integrated Web Search to find the latest Nix packages, community modules, or documentation for specific hardware compatibility.
- Secure Infrastructure Maintenance: Performing system-level repairs and updates without compromising sensitive data, specifically adhering to SOPS security protocols.
| name | nixos |
|---|---|
| description | Resolve NixOS issues using research and sequential thinking |
Use 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.