nix-best-practices
Nix patterns for flakes, overlays, unfree handling, and binary overlays. Use when working with flake.nix or shell.nix.
79
70%
Does it follow best practices?
Impact
91%
1.59xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xbigboss/claude-code/nix-best-practices/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is functional and clearly scoped to Nix ecosystem tooling with an explicit 'Use when' clause. Its main weaknesses are the lack of concrete action verbs (it says 'patterns' rather than specific operations) and incomplete trigger term coverage for the broader Nix ecosystem. It would benefit from more specific capability descriptions and additional trigger keywords.
Suggestions
Replace 'Nix patterns for' with concrete actions like 'Configure Nix flakes, create overlays, enable unfree packages, and set up binary cache overlays'.
Expand trigger terms in the 'Use when' clause to include variations like 'nixpkgs', 'nix develop', 'devShell', 'nix-shell', or 'Nix configuration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Nix) and some specific concepts (flakes, overlays, unfree handling, binary overlays), but describes them as 'patterns' rather than listing concrete actions like 'create flake configurations' or 'configure unfree packages'. | 2 / 3 |
Completeness | Clearly answers both 'what' (Nix patterns for flakes, overlays, unfree handling, binary overlays) and 'when' (Use when working with flake.nix or shell.nix) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'flake.nix', 'shell.nix', 'flakes', and 'overlays' that users would mention, but misses common variations like 'nix-shell', 'nixpkgs', 'nix develop', 'devShell', or 'nix configuration'. | 2 / 3 |
Distinctiveness Conflict Risk | Nix flakes and overlays occupy a very specific niche that is unlikely to conflict with other skills. The mention of specific file types (flake.nix, shell.nix) makes it clearly distinguishable. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference skill with highly actionable, concrete Nix patterns covering flakes, overlays, unfree handling, and binary overlays. Its main weaknesses are verbosity (particularly the binary overlay template and basic dev shell examples that Claude could infer) and lack of explicit workflow sequencing with validation checkpoints. The content would benefit from trimming obvious patterns and restructuring into a concise overview with references to detailed sub-files.
Suggestions
Add explicit validation steps to workflows, e.g., after creating/modifying a flake, always run 'nix flake check' before proceeding, with error recovery guidance.
Move the lengthy binary overlay template and dev shell patterns into separate referenced files to keep SKILL.md as a concise overview.
Remove basic dev shell examples (Basic Shell, With Environment Variables) that Claude can generate without guidance, keeping only the non-obvious patterns like Native Dependencies and the unfree handling nuances.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete code examples, but some sections are longer than necessary. The binary overlay pattern is very verbose with placeholder hashes, and some explanatory text like 'Overlays modify or add packages to nixpkgs' is unnecessary for Claude. The dev shell patterns section includes basic examples Claude could generate without guidance. | 2 / 3 |
Actionability | Nearly all guidance is concrete and executable with complete, copy-paste-ready Nix expressions and bash commands. The flake structure, overlay patterns, binary overlay repo template, and troubleshooting sections all provide specific, actionable code rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | The skill presents patterns and recipes rather than multi-step workflows. While the binary overlay section has an implicit workflow (create overlay → get hashes → apply), it lacks explicit sequencing with validation checkpoints. The troubleshooting section helps with error recovery but isn't integrated into a workflow with feedback loops. The 'nix flake check' command is mentioned but not positioned as a validation step in any workflow. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but it's a monolithic document (~200 lines) that could benefit from splitting the binary overlay pattern and dev shell patterns into separate referenced files. The references to external repos (0xBigBoss/atlas-overlay, 0xBigBoss/bun-overlay) are good but inline content is heavy. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
e437c3c
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.