overthinkos/pixi
languages/skills/pixi/SKILL.md
Pixi package manager binary with environment and PATH setup. Use when working with pixi, conda-forge packages, or Python environment management.
development
Updated Jun 20, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins pixiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 20, 2026, 6:09 AM101.9s1 file scanned
SKILL.md
- name:
- pixi
- description:
- |
pixi -- Pixi package manager
Candy Properties
| Property | Value |
|----------|-------|
| Install files | charly.yml, task: |
Environment Variables
| Variable | Value |
|----------|-------|
| PIXI_CACHE_DIR | ~/.cache/pixi |
| RATTLER_CACHE_DIR | ~/.cache/rattler |
PATH additions: ~/.pixi/bin, ~/.pixi/envs/default/bin
Usage
# charly.yml
my-image:
candy:
- pixi
Used In Boxes
/charly-distros:fedora-builder(direct)/charly-distros:arch-builder(direct)- Transitive dependency via
python/supervisordin most service boxes
Related Candies
/charly-languages:python-- depends on pixi for Python 3.13 installation/charly-coder:pre-commit-- uses pixi for pre-commit installation
Pinned pixi version (var: PIXI_VERSION)
The pixi candy installs a pinned pixi release — var: PIXI_VERSION drives the
releases/download/${PIXI_VERSION}/pixi-${BUILD_ARCH}-unknown-linux-musl.tar.gz
download. Bump PIXI_VERSION (and the candy version:) deliberately to adopt a
newer pixi; do NOT revert to an unpinned releases/latest URL, which makes the
same candy version install a different pixi over time (non-reproducible builds,
against charly's content-hash/CalVer model). Candy pixi.toml files use the
modern [workspace] table (the deprecated [project] form emits a warning under
pixi ≥ 0.70 and is being removed upstream).
Committed pixi.lock → pixi install --frozen
Every pixi candy ships a committed pixi.lock next to its pixi.toml. When a
lock is present, generation auto-flips the build stage from pixi install (a
full SAT solve over the conda + PyPI indexes on every cache miss) to
pixi install --frozen (install straight from the lock — no solve,
deterministic, better cache reuse). The flip is automatic via HasPixiLock
detection (charly/layers.go) → the pixi.toml+lock install command in
the embedded build vocabulary (charly/charly.yml); no per-candy config.
Regenerate the lock whenever you change pixi.toml — --frozen fails the
build loudly if the lock is stale (no silent skew). Generate with the builder's
own pixi so the lock format matches what installs it, e.g.:
charly shell fedora-builder --tag <calver> --bind workspace="$PWD/candy/<name>" \
-c 'grep -q system-requirements pixi.toml || printf "\n[system-requirements]\nlibc = { family = \"glibc\", version = \"2.39\" }\n" >> pixi.toml; pixi lock'
The [system-requirements] glibc fix mirrors what the build stage injects, so
the committed lock resolves the same manylinux wheels the build installs.
When to Use This Skill
Use when the user asks about:
- Pixi package manager setup
- Conda-forge package installation
- Python environment base candy
- The
pixicandy orPIXI_CACHE_DIR
Related
/charly-image:layer— candy authoring reference (charly.ymlschema, task verbs, service declarations)/charly-check:check— declarative testing (check:block,charly check box,charly check live)
Related Skills
overthinkos/plugin
tools
VerifiedTrustedCommunity
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
SKILL.mdUpdated Jun 22, 2026
overthinkos/cue
tools
VerifiedTrustedCommunity
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
SKILL.mdUpdated Jun 16, 2026
overthinkos/egress
tools
VerifiedTrustedCommunity
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
SKILL.mdUpdated Jun 16, 2026
overthinkos/check-k8s
tools
VerifiedTrustedCommunity
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).
SKILL.mdUpdated Jun 14, 2026