overthinkos/ollama-layer
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.
data-ai
Updated May 23, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins ollama-layerInstall 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 23, 2026, 7:03 AM114.3s1 file scanned
SKILL.md
- name:
- ollama-layer
- description:
- |
ollama -- Local LLM inference server
Layer Properties
| Property | Value |
|----------|-------|
| Dependencies | cuda, supervisord |
| Ports | 11434 |
| Volumes | models -> ~/.ollama |
| Aliases | ollama -> ollama |
| Service | ollama (supervisord) |
| Install files | task: |
Environment Variables
| Variable | Value |
|----------|-------|
| OLLAMA_HOST | 0.0.0.0 |
| OLLAMA_MODELS | ~/.ollama/models |
Service Environment (injected into other containers)
| Variable | Template Value | Resolved Example |
|----------|---------------|-----------------|
| OLLAMA_HOST | http://{{.ContainerName}}:11434 | http://ov-ollama:11434 |
Pod-aware: same-container consumers receive http://localhost:11434, cross-container consumers receive http://ov-ollama:11434. When ov config ollama runs, OLLAMA_HOST is automatically injected into the global deploy.yml env. Use ov config ollama --update-all to propagate to already-deployed services immediately.
See /ov-image:layer for env_provides field docs and /ov-core:ov-config for --update-all.
Usage
# image.yml
ollama:
layers:
- ollama
ov alias install ollama # install host 'ollama' command
ollama run llama3 # uses the alias
Used In Images
/ov-ollama:ollama
Cross-Container Integration
The env_provides mechanism makes OLLAMA_HOST available to all containers. The hermes layer 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 /ov-hermes:hermes for details on the auto-provider-configuration.
Tests
The layer ships 3 declarative checks embedded in the org.overthinkos.eval
OCI label (see /ov-eval:eval for the full schema):
- Build-scope (run under
ov eval image):ollama-binary—/usr/bin/ollamaexists
- Deploy-scope (run under
ov eval liveagainst 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/tagsreturns 200ollama-version—ollama --versionstdout matches^ollama version
Related Layers
/ov-distros:cuda-- CUDA toolkit dependency/ov-infrastructure:supervisord-- process manager dependency/ov-openclaw:openclaw-- AI gateway that can use Ollama as backend/ov-hermes:hermes-- AI agent that auto-detectsOLLAMA_HOSTfor local Ollama provider
Related Commands
/ov-core:ov-config— Deploy with quadlet (secrets, volumes, env_provides injection)/ov-core:start— Start the Ollama service/ov-core:service— Manage Ollama service inside container
When to Use This Skill
Use when the user asks about:
- Ollama setup or model management
- LLM serving or inference
- Port 11434 configuration
- Ollama model storage volume
- The
ollamahost alias
Related Skills
overthinkos/agents
development
VerifiedTrustedCommunity
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?".
SKILL.mdUpdated May 31, 2026
overthinkos/workspace-mount
tools
VerifiedTrustedCommunity
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).
SKILL.mdUpdated May 30, 2026
overthinkos/android
development
VerifiedTrustedCommunity
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`.
SKILL.mdUpdated May 26, 2026
overthinkos/git-workflow
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated May 25, 2026