ollama/skills/ollama-layer/SKILL.md
Ollama LLM server on port 11434 with CUDA GPU support and model persistence. Use when working with Ollama, LLM serving, or local AI model inference.
npx skillsauth add overthinkos/overthink-plugins ollama-layerInstall 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 |
|----------|-------|
| Dependencies | cuda, supervisord |
| Ports | 11434 |
| Volumes | models -> ~/.ollama |
| Aliases | ollama -> ollama |
| Service | ollama (supervisord) |
| Install files | task: |
| Variable | Value |
|----------|-------|
| OLLAMA_HOST | 0.0.0.0 |
| OLLAMA_MODELS | ~/.ollama/models |
| Variable | Template Value | Resolved Example |
|----------|---------------|-----------------|
| OLLAMA_HOST | http://{{.ContainerName}}:11434 | http://charly-ollama:11434 |
Pod-aware: same-container consumers receive http://localhost:11434, cross-container consumers receive http://charly-ollama:11434. When charly config ollama runs, OLLAMA_HOST is automatically injected into the global charly.yml env. Use charly config ollama --update-all to propagate to already-deployed services immediately.
See /charly-image:layer for env_provide field docs and /charly-core:charly-config for --update-all.
# charly.yml
ollama:
candy:
- ollama
charly alias install ollama # install host 'ollama' command
ollama run llama3 # uses the alias
/charly-ollama:ollamaThe env_provide mechanism makes OLLAMA_HOST available to all containers. The hermes candy auto-detects this variable and configures itself to use local Ollama as its LLM provider (highest priority in the auto-detection chain: OLLAMA_HOST > OLLAMA_API_KEY > OPENROUTER_API_KEY). See /charly-hermes:hermes for details on the auto-provider-configuration.
The candy ships its acceptance steps in its plan:,
baked into the ai.opencharly.description OCI label (see /charly-check:check
for the full schema). Each step is one inline Op — a probe is a check:
step — and its context: list gates where it runs:
context: [build] (run under charly check box):
ollama-binary — /usr/bin/ollama existscontext: [deploy] (run under charly check live against a live service;
uses ${HOST_PORT:11434} / ${CONTAINER_IP} so deploy-time port remapping
works unchanged):
ollama-tags-api — GET http://${CONTAINER_IP}:${HOST_PORT:11434}/api/tags returns 200ollama-version — ollama --version stdout matches ^ollama version/charly-distros:cuda -- CUDA toolkit dependency/charly-infrastructure:supervisord -- process manager dependency/charly-openclaw:openclaw -- AI gateway that can use Ollama as backend/charly-hermes:hermes -- AI agent that auto-detects OLLAMA_HOST for local Ollama provider/charly-core:charly-config — Deploy with quadlet (secrets, volumes, env_provide injection)/charly-core:start — Start the Ollama service/charly-core:service — Manage Ollama service inside containerUse when the user asks about:
ollama host aliastools
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).