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 well-structured with a clear 'Use when' clause and a distinct niche in Nix configuration. Its main weakness is that it describes topics/patterns rather than concrete actions Claude would perform, and the trigger terms could be broader to capture more Nix-related user queries.
Suggestions
Replace 'Nix patterns for' with concrete actions like 'Creates and configures Nix flakes, sets up overlays, enables unfree packages, and manages binary cache overlays'.
Expand trigger terms in the 'Use when' clause to include variations like 'nixpkgs', 'nix develop', 'devShell', 'derivation', 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 flakes', 'configure overlays', 'enable 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 relevant keywords like 'flake.nix', 'shell.nix', 'flakes', 'overlays', and 'unfree', which users working with Nix would naturally mention. However, it misses common variations like 'nixpkgs', 'nix-shell', 'devShell', 'nix develop', 'derivation', or '.nix files' more broadly. | 2 / 3 |
Distinctiveness Conflict Risk | Nix flakes and shell.nix are a very specific niche. The triggers (flake.nix, shell.nix, overlays, unfree handling) are highly distinctive and 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 excellent concrete code examples covering flakes, overlays, unfree handling, and binary overlays. Its main weaknesses are the monolithic structure (the binary overlay section alone is quite long) and the lack of explicit validation checkpoints in multi-step workflows. Some minor verbosity could be trimmed by removing explanations of concepts Claude already understands.
Suggestions
Add explicit validation steps to multi-step workflows, e.g., 'Run `nix flake check` after applying overlays' or 'Verify hash with `nix-prefetch-url` before committing'.
Extract the lengthy binary overlay pattern into a separate referenced file (e.g., BINARY_OVERLAY.md) and keep only a brief summary with a link in the main skill.
Remove explanatory sentences like 'Overlays modify or add packages to nixpkgs' that describe concepts Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete code examples, but some sections are verbose for a Claude audience—e.g., the full binary overlay pattern is very long and could be summarized with a reference, and the common commands section lists things Claude already knows. Some inline comments like 'Overlays modify or add packages to nixpkgs' explain basics. | 2 / 3 |
Actionability | Nearly every section provides fully executable, copy-paste-ready Nix code with concrete examples. The flake structure, overlay patterns, binary overlay repo, dev shell patterns, and hash-fetching commands are all specific and directly usable. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, multi-step processes like creating a binary overlay repo lack explicit validation checkpoints or sequenced steps. The troubleshooting section helps but there are no feedback loops (e.g., 'validate with nix flake check before proceeding'). The binary overlay workflow involves potentially destructive/complex operations without verification steps. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but it's a monolithic document (~200 lines) where the binary overlay pattern and dev shell patterns could be split into referenced files. There are no cross-references to separate detailed documents; everything is inline. | 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
f772de4
- 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.