ollama/skills/ollama/SKILL.md
Standalone Ollama LLM inference server with CUDA GPU support. Runs as a supervisord service on port 11434 with persistent model storage. MUST be invoked before building, deploying, configuring, or troubleshooting the ollama box.
npx skillsauth add overthinkos/overthink-plugins ollamaInstall 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.
GPU-accelerated Ollama LLM inference server.
| Property | Value | |----------|-------| | Base | nvidia | | Candies | agent-forwarding, ollama | | Platforms | linux/amd64 | | Ports | 11434 | | Registry | ghcr.io/overthinkos |
fedora → nvidia (CUDA base)pixi → python → supervisord (transitive)ollama — LLM server, models volumeollama candy is GPU-agnosticThe ollama candy installs the distro-agnostic Ollama binary (a tarball
extracted to /usr) and a supervisord ollama serve service. The binary
auto-detects the GPU at runtime and falls back to CPU inference when none is
present, so the candy carries no cuda dependency — it only require:s
supervisord. GPU support is a composition choice made at the box level:
ollama box keeps GPU acceleration via base: nvidia (the nvidia
box composes the cuda candy, inherited through the base chain).ollama candy on a non-NVIDIA base and get
CPU inference for free — e.g. /charly-openclaw:openclaw-desktop (cachyos base,
no cuda).| Port | Service | Protocol | |------|---------|----------| | 11434 | Ollama API | HTTP |
| Name | Path | Purpose | |------|------|---------| | models | ~/.ollama | Model storage |
charly box build ollama
charly config ollama
charly start ollama
charly shell ollama -c "ollama pull llama3"
charly shell ollama -c "ollama run llama3 'Hello'"
charly alias install ollama
# Now: ollama pull llama3 (runs inside the container)
When deployed via charly config ollama, this box automatically provides OLLAMA_HOST=http://charly-ollama:11434 to all other deployed containers via the env_provide mechanism. Use --update-all to propagate to already-deployed services:
charly config ollama --update-all
This means containers like jupyter-ml-notebook automatically discover the Ollama endpoint without manual OLLAMA_HOST configuration.
/charly-ollama:ollama — Ollama binary, supervisord service, model volume/charly-distros:cuda — GPU support (via nvidia base)/charly-distros:nvidia — parent (GPU without Ollama)cachyos.ollama is the CachyOS GPU sibling (built on the cachyos.nvidia GPU base) in the overthinkos/cachyos submodule. See /charly-distros:cachyos./charly-openclaw:openclaw-desktop — composes the ollama candy CPU-only (cachyos base, no cuda) alongside a streaming desktop + the openclaw gateway + the nested charly toolchain/charly-jupyter:jupyter-ml-notebook — Jupyter with Ollama integration notebooks (receives OLLAMA_HOST automatically via env_provide when ollama is deployed)/charly-openwebui:openwebui — Open WebUI (receives OLLAMA_HOST via env_provide, auto-configures as OLLAMA_BASE_URL)/charly-ollama:ollama — the Ollama binary candy/charly-jupyter:notebook-ollama — 6 Jupyter notebooks demonstrating Ollama APIs (requests, OpenAI, ollama lib, Anthropic, HuggingFace, GPU)After charly start:
charly status ollama — container runningcharly service status ollama — all services RUNNINGcurl -s http://localhost:11434/api/tags — Ollama API respondsMUST be invoked when the task involves the ollama box, LLM model serving, or the standalone Ollama deployment. Invoke this skill BEFORE reading source code or launching Explore agents.
/charly-image:image — image family umbrella (candy: image entries — those carrying base:/from: — in charly.yml, build/validate/inspect/list)/charly-build:build — the embedded build vocabulary (distros, builders, init-systems)tools
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.
tools
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.
tools
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).
tools
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).