Setup Ollama

What Setup Ollama is

Setup Ollama is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Setup Ollama gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Setup Ollama

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/ai-ml/ollama-local-ai/commands/setup-ollama.md, shared under the repository's MIT license. Read the full file on GitHub.

uname -s

# Using Homebrew (recommended)
brew install ollama

# Start Ollama service
brew services start ollama

# Official installation script
curl -fsSL https://ollama.com/install.sh | sh

# Start service
sudo systemctl start ollama
sudo systemctl enable ollama

ollama --version

# General purpose (4GB)
ollama pull llama3.2

# Code generation (20GB)
ollama pull codellama

# Fast and efficient (4GB)
ollama pull mistral

# Interactive chat
ollama run llama3.2

# Or quick test
echo "Write a hello world in Python" | ollama run llama3.2

curl http://localhost:11434/api/generate -d '{
  "model": "llama3.2",
  "prompt": "Why is the sky blue?"
}'

# Check GPU availability
nvidia-smi

# Ollama automatically uses CUDA if available

# Metal acceleration is automatic on M1/M2/M3

Before you install

• Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
• Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
• Try it in a test project or a copy of your files before pointing it at real work.
• Pin the version you tested, and review changes before updating.
• Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ