tool-pixi

Manage reproducible ML Python environments with Pixi and pixi.lock.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/nishide-dev/claude-code-ml-research --skill tool-pixi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-pixi
Source: https://github.com/nishide-dev/claude-code-ml-research/tree/main/skills/tool-pixi
Command: npx skills add https://github.com/nishide-dev/claude-code-ml-research --skill tool-pixi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the dependency-hell problem in ML projects by helping you create deterministic, hardware-aware Python environments that are consistent across machines and teams.

Core Features & Use Cases

  • Deterministic environment replication: Use pixi.lock to lock exact package versions for repeatable experiments and deployments.
  • GPU/CUDA compatibility checks: Define minimum system requirements (like CUDA and glibc) and let Pixi select compatible binaries before runtime failures occur.
  • Unified conda + PyPI workflow: Mix conda-based system libraries with PyPI packages (often via uv) within one manifest for smoother ML setup.
  • Multi-environment support: Define CPU/GPU and dev/test/prod configurations in one pixi.toml and install or run the exact environment you need.

Example use case: You want a training environment that matches a specific CUDA version for GPU runs, while keeping a separate CPU/MPS-friendly setup for local development and CI—using one manifest and locked outputs.

Quick Start

Use the tool-pixi skill to set up a new ML project environment by initializing pixi in your repository, adding both conda and PyPI dependencies, and installing to generate a reproducible pixi.lock file.

Frequently Asked Questions about tool-pixi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create reproducible ML Python environments with CUDA-aware installs?

Reproducible ML environments with CUDA-aware installs are created using Pixi to resolve dependency and runtime compatibility across local, CI, and GPU servers. You initialize pixi in your repository, add dependencies, and install to generate a deterministic pixi.lock file.

Can I mix conda and PyPI dependencies in a single Pixi manifest for machine learning setup?

Mixing conda-based system libraries with PyPI packages within one Pixi manifest is supported for smoother ML setup. This unified workflow allows you to manage both dependency sources together and lock exact package versions in a pixi.lock file.

What is the best way to manage separate CPU and GPU configurations for ML development?

Managing separate CPU and GPU configurations is best done by defining multi-environment setups for dev, test, and prod in one pixi.toml manifest. Pixi lets you install or run the exact environment you need from this single configuration file.

How does Pixi check GPU and CUDA compatibility before runtime failures occur?

Pixi checks GPU and CUDA compatibility by defining minimum system requirements and using virtual package checks during install and run. This mechanism selects compatible binaries based on your hardware validation before runtime failures occur.

Why do I need a pixi.lock file for deterministic environment replication in ML projects?

A pixi.lock file is needed for deterministic environment replication because it locks exact package versions for repeatable experiments and deployments. It solves the dependency-hell problem by ensuring consistent, hardware-aware Python environments across machines and teams.