overthinkos/uv
ov-coder/skills/uv/SKILL.md
uv + uvx — Astral's fast Python package/project manager. Rewritten 2026-04 to install as a direct-download binary (no pixi env, no Python dep). Pulled via the `download:` verb with `strip_components: 1` to handle the upstream tarball's arch-prefixed top-level directory. Use when working with the uv layer or when deciding whether to install a CLI tool via pixi vs. direct binary download.
tools
Updated May 10, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins uvInstall 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: May 10, 2026, 5:23 AM174.3s1 file scanned
SKILL.md
- name:
- uv
- description:
- |
- via the `download:
- ` verb with `strip_components: 1` to handle the upstream
uv -- Python package / project manager (astral-sh/uv)
Layer Properties
| Property | Value |
|----------|-------|
| Kind | Direct-download binary layer |
| Install files | layer.yml (no pixi.toml, no dependencies) |
| Depends | (none) — uv is a self-contained Rust binary |
| Binaries | /usr/local/bin/uv, /usr/local/bin/uvx |
Why direct download (not pixi)
Pre-2026-04 the layer shipped a pixi.toml with uv = "*" and
requires: python. That installed uv into $HOME/.pixi/envs/default/bin/
as part of a conda-forge Python environment — despite uv being a
completely self-contained Rust binary needing no Python runtime. The
side effects:
- Image bloat — the pixi env drags in ~500 MB of Python stdlib + numpy transitively, nothing of which uv actually uses.
- HOME-dependency — the binary path varied per-image's
$HOME, and HOME-relative PATH entries in child images got subtly wrong when theovauto-intermediate machinery baked uid=1000 paths into images deployed at uid=0 (fixed inov/intermediates.go— see/ov-dev:generate"UID-keyed sibling grouping"). - Confusion — "uv is installed but
which uvsays not found" for anyone who wasn't in a pixi shell.
The rewrite installs uv the way /ov-coder:typst and
/ov-foundation:pixi itself already did — fetch the upstream binary,
unpack to /usr/local/bin, done. System-wide reachable, always on
PATH, no HOME gymnastics.
Install task
tasks:
- download: "https://github.com/astral-sh/uv/releases/latest/download/uv-${BUILD_ARCH}-unknown-linux-gnu.tar.gz"
extract: tar.gz
strip_components: 1
to: /usr/local/bin
user: root
${BUILD_ARCH} expands to x86_64 / aarch64 at build time. Upstream
ships per-arch tarballs under stable latest-download URLs, nested one
level deep (uv-x86_64-unknown-linux-gnu/uv, …/uvx). The
strip_components: 1 modifier (new in 2026-04, see /ov-build:layer
"Download verb") collapses that wrapper so both binaries land
directly at /usr/local/bin/uv and /usr/local/bin/uvx.
Tests
Three build-scope tests ship with the layer:
| Test | Purpose |
|---|---|
| uv-binary | /usr/local/bin/uv exists |
| uv-version | uv --version exits 0 |
| uvx-binary | /usr/local/bin/uvx exists (the per-run tool runner) |
Used In Images
/ov-coder:fedora-coder— the canonical kitchen-sink dev image.- Any image composing
hermes-fullor directly includinguv.
Related Layers
/ov-foundation:pixi— direct-download pattern this layer now mirrors. Pixi remains a legitimate multi-binary Python env manager for images that genuinely need one (jupyter, whisper, openwebui); uv is too small to justify the overhead./ov-coder:typst— sibling direct-download binary pattern./ov-foundation:python— the pixi-python meta-layer this layer no longer depends on./ov-coder:rust— system Rust toolchain, if you want to build uv from source instead (cargo install uv). Usually not worth it — the Astral binary is pre-optimized.
Related Commands
/ov-build:layer— authoring reference (coversdownload:verb +strip_components:modifier)/ov-core:shell— runuvinside a container
When to Use This Skill
MUST be invoked when:
- Adding
uvto an image's layer list. - Authoring a sibling layer for a small Rust/Go CLI tool — this is the canonical pattern (direct download > pixi > anything else).
- Debugging why
uv --versionfails: it's a$PATHor binary-landing- at-wrong-path issue, not a Python env problem. - Understanding why "uv has no dependencies" is correct even though it manages Python packages.
Related
/ov-build:eval— declarative testing (eval:block,ov eval image,ov eval 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