Automates the installation and configuration of Ollama for local, private AI model inference.

Install

mkdir -p .claude/skills/ollama-setup && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1607" && unzip -o skill.zip -d .claude/skills/ollama-setup && rm skill.zip

Installs to .claude/skills/ollama-setup

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Configure auto-configure Ollama when user needs local LLM deployment,
69 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Detect the host operating system and available hardware
  • Select appropriate models based on available RAM
  • Install Ollama using platform-appropriate methods
  • Pull recommended models
  • Verify installation by listing models and running a test prompt
  • Configure integration with target applications

How it works

This skill detects the operating system and hardware, selects optimal models based on RAM, installs Ollama via platform-specific commands, pulls the chosen model, and verifies the setup.

Inputs & outputs

You give it
User request for local LLM deployment or specific model installation
You get back
Ollama installation confirmed and running, selected model(s) pulled, REST API endpoint accessible, integration code snippet, hardware assessment report, perform

When to use ollama-setup

  • Deploy local LLMs without API costs
  • Run privacy-focused AI models offline
  • Switch from OpenAI to local alternatives
  • Assess hardware for model capability

About this skill

Ollama Setup

Overview

Auto-configure Ollama for local LLM deployment, eliminating hosted API costs and enabling offline AI inference. This skill handles system assessment, model selection based on available hardware (RAM, GPU), installation across macOS/Linux/Docker, and integration with Python, Node.js, and REST API clients.

Prerequisites

  • macOS 12+, Linux (Ubuntu 20.04+, Fedora 36+), or Docker runtime
  • Minimum 8 GB RAM for 7B parameter models; 16 GB for 13B models; 32 GB+ for 70B models
  • Optional: NVIDIA GPU with CUDA drivers for accelerated inference (nvidia-smi to verify)
  • Optional: Apple Silicon (M1/M2/M3) for Metal-accelerated inference on macOS
  • Disk space: 4-40 GB depending on model size (quantized weights)
  • Package manager: brew (macOS), curl (Linux), or docker (containerized)

Instructions

  1. Detect the host operating system and available hardware using uname -s, free -h (Linux) or vm_stat (macOS), and nvidia-smi (if GPU present)
  2. Select appropriate models based on available RAM:
    • 8 GB: llama3.2:7b (4 GB), mistral:7b (4 GB), phi3:14b (8 GB)
    • 16 GB: codellama:13b (7 GB), mixtral:8x7b (26 GB quantized)
    • 32 GB+: llama3.2:70b (40 GB), codellama:34b (20 GB)
  3. Install Ollama using the platform-appropriate method:
    • macOS: brew install ollama && brew services start ollama
    • Linux: curl -fsSL https://ollama.com/install.sh | sh && sudo systemctl start ollama
    • Docker: docker run -d -v ollama:/root/.ollama -p 11434:11434 --name ollama ollama/ollama
  4. Pull the recommended model: ollama pull llama3.2
  5. Verify the installation by listing available models (ollama list) and running a test prompt (ollama run llama3.2 "Say hello")
  6. Confirm the REST API is accessible: curl http://localhost:11434/api/tags
  7. Configure integration with the target application using the appropriate client library (Python ollama, Node.js ollama, or raw HTTP)
  8. Set up GPU acceleration if NVIDIA or Apple Silicon hardware is detected
  9. Configure model persistence and cache directory if non-default storage location is required
  10. Validate end-to-end inference latency and throughput for the selected model

See ${CLAUDE_SKILL_DIR}/references/skill-workflow.md for the detailed workflow with code snippets.

Output

  • Ollama installation confirmed and running as a system service or Docker container
  • Selected model(s) pulled and cached locally with verified inference capability
  • REST API endpoint accessible at http://localhost:11434
  • Integration code snippet for the target language (Python, Node.js, or cURL)
  • Hardware assessment report: OS, RAM, GPU availability, recommended models
  • Performance baseline: tokens per second for the selected model on local hardware

Error Handling

ErrorCauseSolution
ollama: command not foundInstallation incomplete or PATH not updatedRe-run install script; restart shell session; verify /usr/local/bin/ollama exists
Model pull fails with timeoutNetwork connectivity issue or Ollama registry unreachableCheck internet connection; retry with ollama pull --insecure behind corporate proxy
Out of memory during inferenceModel size exceeds available RAMSwitch to a smaller quantized model (e.g., 7B instead of 13B); close memory-intensive applications
GPU not detectedCUDA drivers missing or incompatible versionInstall CUDA toolkit >= 11.8; verify with nvidia-smi; restart Ollama service after driver install
Port 11434 already in useAnother service occupying the default Ollama portStop conflicting service; or set OLLAMA_HOST=0.0.0.0:11435 environment variable

See ${CLAUDE_SKILL_DIR}/references/errors.md for additional error scenarios.

Examples

Scenario 1: Developer Workstation Setup -- Install Ollama on a macOS M2 machine with 16 GB RAM. Pull codellama:13b for code generation tasks. Integrate with a Python FastAPI application using the ollama Python package. Expected throughput: 30-50 tokens/second on Apple Silicon.

Scenario 2: Air-Gapped Server Deployment -- Install Ollama on an offline Ubuntu server via pre-downloaded binary. Transfer model weights via USB. Configure as a systemd service with auto-restart. Serve llama3.2:7b via REST API for internal team use.

Scenario 3: Docker-Based CI Pipeline -- Run Ollama in a Docker container as part of a CI/CD pipeline for automated code review. Pull mistral:7b, expose the API on port 11434, and integrate with a Node.js test harness that sends code diffs for analysis.

Resources

Prerequisites

macOS 12+, Linux (Ubuntu 20.04+, Fedora 36+), or Docker runtimeMinimum 8 GB RAM for 7B parameter modelsDisk space: 4-40 GB depending on model sizePackage manager: brew (macOS), curl (Linux), or docker (containerized)

Limitations

  • Model pull fails with timeout due to network connectivity issues or Ollama registry being unreachable
  • Out of memory during inference if model size exceeds available RAM
  • GPU not detected if CUDA drivers are missing or incompatible

How it compares

This skill automates the entire Ollama setup and model configuration process, unlike manual installation which requires separate steps for system assessment, model selection, and integration.

Compared to similar skills

ollama-setup side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
ollama-setup (this skill)1127dReviewBeginner
genkit-production-expert027dReviewAdvanced
mcp-builder1363moReviewAdvanced
azure-functions105moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

generating-trading-signals

jeremylongshore

Generate trading signals using technical indicators (RSI, MACD, Bollinger Bands, etc.). Combines multiple indicators into composite signals with confidence scores. Use when analyzing assets for trading opportunities or checking technical indicators. Trigger with phrases like "get trading signals", "check indicators", "analyze for entry", "scan for opportunities", "generate buy/sell signals", or "technical analysis".

725

You might also like

genkit-production-expert

jeremylongshore

Build production Firebase Genkit applications including RAG systems, multi-step flows, and tool calling for Node.js/Python/Go. Deploy to Firebase Functions or Cloud Run with AI monitoring. Use when asked to "create genkit flow" or "implement RAG". Trigger with relevant phrases based on skill purpose.

01

mcp-builder

anthropics

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

136215

azure-functions

aj-geddes

Create serverless functions on Azure with triggers, bindings, authentication, and monitoring. Use for event-driven computing without managing infrastructure.

10104

copilot-sdk

github

Build agentic applications with GitHub Copilot SDK. Use when embedding AI agents in apps, creating custom tools, implementing streaming responses, managing sessions, connecting to MCP servers, or creating custom agents. Triggers on Copilot SDK, GitHub SDK, agentic app, embed Copilot, programmable agent, MCP server, custom agent.

763

openrouter-function-calling

jeremylongshore

Implement function/tool calling with OpenRouter models. Use when building agents or structured outputs. Trigger with phrases like 'openrouter functions', 'openrouter tools', 'openrouter agent', 'function calling'.

539

ai-agents-architect

davila7

Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build agent, AI agent, autonomous agent, tool use, function calling.

534

Search skills

Search the agent skills registry