# Manage Reproducible Python Environments

Scientific Python teams often need reproducible environments across conda and PyPI packages. This skill gives practical Pixi workflows for setup, dependency groups, tasks, migration, and CI.

## Install

```bash
npx skillstore add codingkaiser/pixi-package-manager
```

## Metadata

- Status: approved
- Slug: codingkaiser-pixi-package-manager
- Skillstore revision: r1
- Version status: missing
- Tree hash: d1897a182c0260f4c210770cc408c6b46de5fe3624888c90ac6db418d2992e45
- Author: CodingKaiser
- GitHub username: CodingKaiser
- License: MIT
- Repository: https://github.com/CodingKaiser/claude-kaiser-skills/tree/main/pixi
- Ref: 02f077c174c5335e2f5d02ca15e77b70d9543e58
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: blocked
- Manual install advisory: allowed\_with\_warning
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/codingkaiser-pixi-package-manager
- Manifest: https://skillstore.pages.dev/api/skills/codingkaiser-pixi-package-manager/manifest

## Capabilities

- Plan new Pixi projects that use pyproject.toml and pixi.lock.
- Choose conda-forge or PyPI dependencies based on package type and platform needs.
- Organize features, environments, and tasks for development, testing, and production.
- Migrate requirements.txt or environment.yml workflows into Pixi projects.
- Design CI workflows that install dependencies, run tests, and use lockfiles.
- Troubleshoot solver, build, activation, and lockfile problems.

## Use Cases

- Start a Research Project: Create a reproducible Pixi environment for notebooks, tests, and scientific libraries.
- Migrate Existing Dependencies: Convert requirements.txt or environment.yml workflows into a cleaner Pixi project layout.
- Standardize CI Environments: Use lockfiles and Pixi tasks to make test and build jobs more repeatable.

## Prompt Templates

### Create a New Pixi Project

```
Create a Pixi setup plan for a new scientific Python project. Include dependencies, environments, tasks, and files I should commit.
```

### Migrate Existing Dependencies

```
Review my current dependency list and propose a Pixi migration plan. Separate conda-forge packages, PyPI packages, dev tools, and optional features.
```

### Design Multi-Environment Tasks

```
Design Pixi environments and tasks for development, testing, documentation, and production. Explain how each environment should be used.
```

### Optimize Pixi CI

```
Analyze my CI workflow for Pixi. Recommend safer installation, caching, lockfile use, and task structure for reliable builds.
```

## Limitations

- Pixi must already be installed or available in the target environment.
- The skill does not verify third-party package safety or repository trust.
- Complex scientific stacks may still need platform-specific constraints.
- Package availability depends on configured channels and operating systems.

## Best Practices

- Commit pixi.lock and review lockfile changes in pull requests.
- Use conda-forge for compiled scientific dependencies and PyPI for pure Python gaps.
- Prefer pixi run tasks for automation so environments are explicit and repeatable.

## Anti Patterns

- Do not mix unmanaged pip installs into a Pixi environment without tracking them.
- Do not use broad version ranges for critical production or research dependencies.
- Do not execute remote installers in CI without verification or a trusted setup action.

## Security Audit

- Audited at: 2026-07-05T06:38:39.437\+00:00
- Summary: The audit confirms one critical supply-chain issue: a CI example pipes a remote Pixi installer directly into bash. It also confirms medium-risk shell-hook eval guidance; the remaining static matches are markdown examples, resource links, placeholder paths, or prose-only false positives.

## Stats

- Views: 311
- Downloads: 9
- Favorites: 0
- Popularity score: 0