Nixos Best Practices
CheckedApplies NixOS best practices—configuration management, declarative infrastructure, reproducible builds—for optimized system setup.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add lihaoze123/my-claude-code --skill nixos-best-practices -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
lihaoze123
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned lihaoze123/my-skills at 03a65e39a2.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 03a65e39a2
- Scanned
- 9 files, 2,305 lines
About this skill
What it does
This skill helps AI agents configure NixOS systems using flakes, manage overlays effectively, and structure configurations for maintainability. It emphasizes following established best practices within the NixOS ecosystem, ensuring reproducible builds and optimized system setup. The skill guides users to avoid common pitfalls by referencing relevant rule files and documentation before making configuration changes.
When to use it
- Configuring NixOS with flakes and Home Manager
- Troubleshooting issues where overlays don't seem to apply correctly
- Implementing
useGlobalPkgs = truewith custom overlays - Organizing NixOS configurations across multiple hosts
- Diagnosing situations where package changes aren’t appearing after a rebuild
Key capabilities
- Flakes configuration management
- Overlay scope and application understanding (particularly in relation to
useGlobalPkgs) - Structuring host configurations for organization
- Package installation best practices within NixOS
- Guidance on avoiding common configuration mistakes
- Systematic debugging approaches for NixOS issues
Example prompts
- "How do I configure overlays when using
useGlobalPkgs = true?" - "What is the correct structure for a NixOS flake configuration?"
- "I'm having trouble with an overlay not applying. What should I check?"
Tips & gotchas
- Read the documentation first: Before making any changes, review the relevant rule files (
overlay-scope,flakes-structure, etc.) andcommon-mistakes.md. - Overlay placement is critical: When using
useGlobalPkgs = true, overlays must be defined in the NixOS configuration block, not within Home Manager files. - Avoid guesswork: Consult documentation rather than experimenting with options or assuming functionality.