Ollama
Deploy and serve local models with Ollama — pull and run them, then expose the OpenAI-compatible endpoint to apps and agents.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Ollama when an AI agent needs a reusable SKILL.md workflow for this job: Deploy and serve local models with Ollama — pull and run them, then expose the OpenAI-compatible endpoint to apps and agents.
When not to use it
Skip Ollama when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/ollama # Save SKILL.md to ~/.claude/skills/ollama/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/ollama/SKILL.md. For a shared project, commit the folder at .claude/skills/ollama/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Ollama skill for this task: Use Ollama when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
69/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 73/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptinferred
The skill text mentions ChatGPT or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamainferred
The skill text mentions Llama or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Ollama Serving
Ollama runs open-weight models locally with automatic GPU detection and an OpenAI-compatible API on `http://localhost:11434`.
## Before you start
If the user's message only invokes this skill (e.g. "use ollama skill") without a concrete request, ask the user what they want. Do not run any command until the goal is clear.
Ask the user which model to run; if they have no preference, recommend the small default [Qwen/Qwen3.5-0.8B](https://huggingface.co/Qwen/Qwen3.5-0.8B) (`ollama pull qwen3.5:0.8b`). The model must fit the machine's RAM/VRAM.
Ollama runs everywhere — macOS, Linux and Windows, on CPUs as well as NVIDIA/AMD GPUs — so engine choice follows the user's preference: Ollama is the simple default, while vLLM targets high-throughput GPU serving. Check the current state first:
```bash ollama --version # is Ollama installed? ollama ps # is the service already serving models? ```
If port 11434 is already serving, reuse that instance — never kill an existing Ollama process.
## Suggested workflow
1. Ask the user which model to run; with no preference, recommend [Qwen/Qwen3.5-0.8B](https://huggingface.co/Qwen/Qwen3.5-0.8B) (`qwen3.5:0.8b`). 2. Pick the engine the user prefers: Ollama is the default; vLLM covers high-throughput GPU serving. 3. Install Ollama if missing, then `ollama pull qwen3.5:0.8b`. 4. Verify with `curl http://localhost:11434/v1/models`. 5. Register the endpoint: `penguin config model add ... --client-type openai-chat --base-url http://localhost:11434/v1` — a pulled Ollama model is not visible to Penguin until added. 6. Confirm the new entry with `penguin config model list`.
## Install
```bash curl -fsSL https://ollama.com/install.sh | sh # Linux; macOS/Windows use the desktop app ```
The service then listens on `http://localhost:11434`.
## Pull and run
```bash ollama pull qwen3.5:0.8b # download a model ollama run qwen3.5:0.8b # interactive chat (pulls first if missing) ollama list # downloaded models ollama ps # models loaded in memory ollama stop qwen3.5:0.8b # unload a model ```
## OpenAI-compatible endpoint
The endpoint is `http://localhost:11434/v1`; any non-empty API key is accepted (conventionally `ollama`):
```bash curl http://localhost:11434/v1/models ```
## Context length
The default context window is small, and agent sessions need a large one. Raise it in the server's environment:
```bash OLLAMA_CONTEXT_LENGTH=32768 ollama serve # systemd service: set it via `systemctl edit ollama` ```
Or bake it into a model variant with a Modelfile:
``` FROM qwen3.5:0.8b PARAMETER num_ctx 32768 ```
```bash ollama create qwen3.5-32k -f Modelfile ```
## Register with PenguinHarness
Model configuration is the penguin CLI's job — `penguin config model add` registers an endpoint and `penguin config model list` shows what has been registered. A pulled Ollama model is not visible to Penguin until you add it:
```bash penguin config model add --provider custom --client-type openai-chat \ --base-url http://localhost:11434/v1 --model-id qwen3.5:0.8b --api-key ollama penguin config model list # the new entry should now be listed ```
Intended uses
- Use Ollama when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.