ov-layers/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.
npx skillsauth add overthinkos/overthink-plugins pixiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Install files | layer.yml, tasks: |
| Variable | Value |
|----------|-------|
| PIXI_CACHE_DIR | ~/.cache/pixi |
| RATTLER_CACHE_DIR | ~/.cache/rattler |
PATH additions: ~/.pixi/bin, ~/.pixi/envs/default/bin
# image.yml
my-image:
layers:
- pixi
/ov-images:fedora-builder (direct)/ov-images:archlinux-builder (direct)python / supervisord in most service images/ov-layers:python -- depends on pixi for Python 3.13 installation/ov-layers:pre-commit -- uses pixi for pre-commit installationUse when the user asks about:
pixi layer or PIXI_CACHE_DIR/ov:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov:test — declarative testing (tests: block, ov image test, ov test)development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.