Skip to content
TrustedSkillsbeta
Back to all skills

Nix Packaging Best Practices

Checked
lihaoze123·vlatest·backend

Generates Nix expressions adhering to best practices for reproducible, maintainable package builds and configurations.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add lihaoze123/my-claude-code --skill nix-packaging-best-practices -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to 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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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
Manifest
skills/nix-packaging-best-practices/SKILL.md
Scanned
16 files, 3,602 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides guidance and recommendations for creating robust and reproducible Nix packages. It helps users understand how to structure their flake.nix files, manage dependencies effectively, and ensure consistent builds across different environments. The focus is on applying best practices within the Nix ecosystem for software packaging.

When to use it

  • You're starting a new Nix package and want to follow established conventions.
  • Your existing Nix packages are failing or producing inconsistent results.
  • You need help understanding how to properly define dependencies in your flake.nix.
  • You’re looking for advice on structuring your project directory for optimal Nix integration.

Key capabilities

  • Flake structure guidance
  • Dependency management best practices
  • Reproducible builds
  • Understanding of flake.nix files

Example prompts

  • "How should I structure my flake.nix file for a Go application?"
  • "What are the best practices for managing dependencies in Nix?"
  • "Can you help me troubleshoot why my Nix build is failing?"

Tips & gotchas

  • A basic understanding of Nix and its terminology is helpful to get the most out of this skill.
  • Nix can be complex; start with small, well-defined packages before tackling larger projects.