ov-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 image.
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 | | Layers | agent-forwarding, ollama | | Platforms | linux/amd64 | | Ports | 11434 | | Registry | ghcr.io/overthinkos |
fedora → nvidia (CUDA base)pixi → python → supervisord (transitive)ollama — LLM server, models volume| Port | Service | Protocol | |------|---------|----------| | 11434 | Ollama API | HTTP |
| Name | Path | Purpose | |------|------|---------| | models | ~/.ollama | Model storage |
ov image build ollama
ov config ollama
ov start ollama
ov shell ollama -c "ollama pull llama3"
ov shell ollama -c "ollama run llama3 'Hello'"
ov alias install ollama
# Now: ollama pull llama3 (runs inside the container)
When deployed via ov config ollama, this image automatically provides OLLAMA_HOST=http://ov-ollama:11434 to all other deployed containers via the env_provides mechanism. Use --update-all to propagate to already-deployed services:
ov config ollama --update-all
This means containers like jupyter-ml-notebook automatically discover the Ollama endpoint without manual OLLAMA_HOST configuration.
/ov-ollama:ollama — Ollama binary, supervisord service, model volume/ov-foundation:cuda — GPU support (via nvidia base)/ov-foundation:nvidia — parent (GPU without Ollama)/ov-openclaw:openclaw-ollama — OpenClaw gateway + Ollama/ov-openclaw:openclaw-ollama-sway-browser — full stack with desktop/ov-jupyter:jupyter-ml-notebook — Jupyter with Ollama integration notebooks (receives OLLAMA_HOST automatically via env_provides when ollama is deployed)/ov-openwebui:openwebui — Open WebUI (receives OLLAMA_HOST via env_provides, auto-configures as OLLAMA_BASE_URL)/ov-ollama:ollama — the Ollama binary layer/ov-jupyter:notebook-ollama — 6 Jupyter notebooks demonstrating Ollama APIs (requests, OpenAI, ollama lib, Anthropic, HuggingFace, GPU)After ov start:
ov status ollama — container runningov service status ollama — all services RUNNINGcurl -s http://localhost:11434/api/tags — Ollama API respondsMUST be invoked when the task involves the ollama image, LLM model serving, or the standalone Ollama deployment. Invoke this skill BEFORE reading source code or launching Explore agents.
/ov-build:image — image family umbrella (image: entries in overthink.yml, build/validate/inspect/list)/ov-build:build — build.yml 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).