pixi-package-manager

Unify conda-forge and PyPI dependencies into a single cross-platform lockfile.

6|1|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/CodingKaiser/kaiser-skills --skill pixi-package-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pixi-package-manager
Source: https://github.com/CodingKaiser/kaiser-skills/tree/main/pixi
Command: npx skills add https://github.com/CodingKaiser/kaiser-skills --skill pixi-package-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pixi unifies conda-forge and PyPI dependency management, enabling reproducible environments for scientific Python projects and preventing drift between development and production.

Core Features & Use Cases

  • Unified Package Management: resolves dependencies from both conda-forge and PyPI in a single graph.
  • Multi-Platform Lockfiles: generate pixi.lock containing platform-specific specifications for Linux, macOS, and Windows.
  • pyproject.toml Integration: reads project metadata from pyproject.toml to align packaging workflows.
  • Task Automation: defines reusable tasks to automate install, test, and build workflows.

Quick Start

  • Create a new pixi project: pixi init --format pyproject
  • Add core dependencies: pixi add numpy scipy pandas
  • Install and lock: pixi install

Frequently Asked Questions about pixi-package-manager

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

FAQPage Schema
How do I unify conda and PyPI dependencies in a single reproducible environment?

To unify conda and PyPI dependencies for a reproducible environment, this Skill resolves packages from both sources into a single dependency graph. It enforces deterministic workflows by generating a single cross-platform lockfile within your pyproject.toml configuration.

How do I generate a cross-platform lockfile for Linux, macOS, and Windows using pyproject.toml?

Generating a cross-platform lockfile for Linux, macOS, and Windows is achieved by resolving dependencies within a pyproject.toml configuration. The process creates a pixi.lock file containing platform-specific specifications to ensure deterministic installations across operating systems.

What is the best way to manage multi-platform scientific Python projects with conda-forge and PyPI?

The best way to manage multi-platform scientific Python projects with conda-forge and PyPI is by unifying their dependency graphs within a pyproject.toml configuration. This approach prevents drift between development and production by enforcing a single cross-platform lockfile.

Can I automate install, test, and build tasks within a unified conda and PyPI workflow?

You can automate install, test, and build tasks within a unified conda and PyPI workflow by defining reusable task-based commands. This task automation integrates directly with the pyproject.toml configuration to execute deterministic workflows across platforms.

Does this dependency management approach support multi-platform projects without separate lockfiles?

This dependency management approach supports multi-platform projects by enforcing a single cross-platform lockfile. Instead of maintaining separate lockfiles, it generates a unified pixi.lock containing platform-specific specifications for Linux, macOS, and Windows.

Why does my scientific Python environment drift between development and production?

Scientific Python environments drift between development and production due to unresolved dependency conflicts across conda-forge and PyPI. Unifying these dependency graphs and enforcing a cross-platform lockfile prevents this drift and ensures reproducible environments.