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 reasonably effective with a clear niche and explicit trigger guidance. Its main weakness is that it describes topics ('patterns for flakes, overlays') rather than concrete actions Claude would perform, and it could benefit from broader trigger term coverage for the Nix ecosystem.
Suggestions
Replace 'Nix patterns for' with concrete actions like 'Creates and configures Nix flake definitions, adds package overlays, handles unfree package allowlisting, and sets up binary cache overlays'.
Expand trigger terms to include common variations like 'nixpkgs', 'devShell', 'nix develop', 'derivation', 'nix-shell', or '.nix files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Nix) and lists some specific concepts (flakes, overlays, unfree handling, binary overlays), but describes them as 'patterns' rather than concrete actions. It doesn't specify what actions are performed (e.g., 'create flake configurations', 'add overlay definitions'). | 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 relevant keywords like 'flake.nix', 'shell.nix', 'flakes', 'overlays', and 'unfree' which users working with Nix would naturally use. However, it misses common variations like 'nix-shell', 'nixpkgs', 'devShell', 'nix develop', or 'derivation'. | 2 / 3 |
Distinctiveness Conflict Risk | Nix flakes and shell.nix are a very specific niche. The triggers 'flake.nix' and 'shell.nix' are highly distinctive file names unlikely to conflict with other skills. | 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, actionable Nix reference with concrete, executable code examples covering the key patterns described. Its main weaknesses are the monolithic structure (everything inline rather than using progressive disclosure) and the lack of explicit validation/verification steps in multi-step processes like creating binary overlays or applying overlays. The content is genuinely useful and mostly efficient, though some sections could be tightened.
Suggestions
Add explicit validation steps to multi-step processes, e.g., after applying overlays run 'nix flake check' and after creating binary overlay repos run 'nix build .#tool' to verify the package builds correctly.
Split the binary overlay pattern and dev shell patterns into separate referenced files, keeping SKILL.md as a concise overview with links to detailed guides.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary explanations (e.g., 'Overlays modify or add packages to nixpkgs') and could be tightened in places. The binary overlay section is quite lengthy with placeholder hashes that add bulk. However, most content is genuinely useful Nix-specific knowledge that Claude wouldn't inherently know. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready Nix code for every pattern discussed—flake structure, overlays, unfree handling, binary overlays, dev shells, direnv integration, and CLI commands. The code examples are complete and concrete with specific syntax. | 3 / 3 |
Workflow Clarity | The skill presents patterns clearly but lacks explicit validation checkpoints and sequenced workflows. For example, the binary overlay creation doesn't have a 'build and test' verification step, and the overlay application section doesn't mention checking that overlays were applied correctly. The troubleshooting section partially compensates but is reactive rather than preventive. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but it's a monolithic document (~200 lines) with no references to external files. The binary overlay pattern and dev shell patterns could be split into separate reference files, with SKILL.md serving as a concise overview pointing to them. | 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
83d60e9
- 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.