agentleFS
DingyangLyuDingyangLyu/MatClaw/.claude/skills/add-ollama-tool/SKILL.md

add-ollama-tool

Skill98 starsChanged 8 months agoApache-2.0View on GitHub

Add Ollama MCP server so the container agent can call local models for cheaper/faster tasks like summarization, translation, or general queries.

  • Reads credentials

9 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-anydoc, add-clidash and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TomGranotSkill

    add-anydoc

    Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when agents need to read attached Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, or text-based PDF files without uploading them to a hosted parser.

    Also in 5 projects that use this

  • TomGranotSkill

    add-clidash

    Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.

    Also in 5 projects that use this

  • qwibitaiSkill

    add-iron-proxy

    Install or refresh Iron Proxy and its official Iron Control web console for NanoClaw. Use when selecting the Iron gateway, adding its management UI, configuring credentials and grants, or restoring the proxy, approval bridge, and agent guidance.

    Also in 4 projects that use this

  • qwibitaiSkill

    add-mattermost

    Add a self-hosted or cloud Mattermost bot channel through the Chat SDK bridge, reusing a healthy server when available and linking to official server setup guidance when needed.

    Also in 4 projects that use this

  • b1rdmaniaSkill

    migrate-memory

    Migrate from monolith CLAUDE.md to the three-file memory system (identity + state + log). Non-destructive — backs up the original first.

    Also in 6 projects that use this

  • nanocoaiSkill

    add-cursor

    Use Cursor (local Agent SDK) as a full agent provider — planning, tool orchestration, MCP tools, session resume — alongside or instead of Claude. Cursor-account sign-in or API key, held by the credential gateway. Per-group via `ncl groups config update --provider cursor`. Distinct from using Cursor as a cloud agent (those run on Cursor VMs and are not this provider).

    Also in 3 projects that use this

  • +5 more from TomGranot
  • +1 more from qwibitai

The file

We split this skill into the rules it gives an agent

11 rules. 2 are common, 4 are distinctive, and 5 are very specific to this project.

  • 2

    Common

    Most of the 9 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .matclaw/state.yaml. If ollama is in applied_skills, skip to Phase 3 (Configure).

    line 18
  2. Common:

    Verify Ollama is installed and running on the host:

    line 22
  3. Distinctive:

    If Ollama is not installed, direct the user to https://ollama.com/download.

    line 28
  4. Common:

    If no models are installed, suggest pulling one:

    line 30
  5. Distinctive:

    Run the skills engine to apply this skill's code package.

    line 42
  6. Very specific:

    If .matclaw/ directory doesn't exist yet:

    line 46
  7. Distinctive:

    If the apply reports merge conflicts, read the intent files:

    line 65
  8. Distinctive:

    Run the watcher script for macOS notifications when Ollama is used:

    line 118
  9. Very specific:

    Verify Ollama is running: ollama list

    line 146
  10. Very specific:

    Check Docker can reach the host: docker run --rm curlimages/curl curl -s http://host.docker.internal:11434/api/tags

    line 147
  11. Very specific:

    If using a custom host, check OLLAMA_HOST in .env

    line 148

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add Ollama Integration

This skill adds a stdio-based MCP server that exposes local Ollama models as tools for the container agent. Claude remains the orchestrator but can offload work to local models.

Tools added:

  • ollama_list_models — lists installed Ollama models
  • ollama_generate — sends a prompt to a specified model and returns the response

Phase 1: Pre-flight

Check if already applied

Read .matclaw/state.yaml. If ollama is in applied_skills, skip to Phase 3 (Configure). The code changes are already in place.

Check prerequisites

Verify Ollama is installed and running on the host:

ollama list

If Ollama is not installed, direct the user to https://ollama.com/download.

If no models are installed, suggest pulling one:

You need at least one model. I recommend:

ollama pull gemma3:1b    # Small, fast (1GB)
ollama pull llama3.2     # Good general purpose (2GB)
ollama pull qwen3-coder:30b  # Best for code tasks (18GB)

Phase 2: Apply Code Changes

Run the skills engine to apply this skill's code package.

Initialize skills system (if needed)

If .matclaw/ directory doesn't exist yet:

npx tsx scripts/apply-skill.ts --init

Apply the skill

npx tsx scripts/apply-skill.ts .claude/skills/add-ollama-tool

This deterministically:

  • Adds container/agent-runner/src/ollama-mcp-stdio.ts (Ollama MCP server)
  • Adds scripts/ollama-watch.sh (macOS notification watcher)
  • Three-way merges Ollama MCP config into container/agent-runner/src/index.ts (allowedTools + mcpServers)
  • Three-way merges [OLLAMA] log surfacing into src/container-runner.ts
  • Records the application in .matclaw/state.yaml

If the apply reports merge conflicts, read the intent files:

  • modify/container/agent-runner/src/index.ts.intent.md — what changed and invariants
  • modify/src/container-runner.ts.intent.md — what changed and invariants

Copy to per-group agent-runner

Existing groups have a cached copy of the agent-runner source. Copy the new files:

for dir in data/sessions/*/agent-runner-src; do
  cp container/agent-runner/src/ollama-mcp-stdio.ts "$dir/"
  cp container/agent-runner/src/index.ts "$dir/"
done

Validate code changes

npm run build
./container/build.sh

Build must be clean before proceeding.

Phase 3: Configure

Set Ollama host (optional)

By default, the MCP server connects to http://host.docker.internal:11434 (Docker Desktop) with a fallback to localhost. To use a custom Ollama host, add to .env:

OLLAMA_HOST=http://your-ollama-host:11434

Restart the service

launchctl kickstart -k gui/$(id -u)/com.matclaw  # macOS
# Linux: systemctl --user restart matclaw

Phase 4: Verify

Test via WhatsApp

Tell the user:

Send a message like: "use ollama to tell me the capital of France"

The agent should use ollama_list_models to find available models, then ollama_generate to get a response.

Monitor activity (optional)

Run the watcher script for macOS notifications when Ollama is used:

./scripts/ollama-watch.sh

Check logs if needed

tail -f logs/matclaw.log | grep -i ollama

Look for:

  • Agent output: ... Ollama ... — agent used Ollama successfully
  • [OLLAMA] >>> Generating — generation started (if log surfacing works)
  • [OLLAMA] <<< Done — generation completed

Troubleshooting

Agent says "Ollama is not installed"

The agent is trying to run ollama CLI inside the container instead of using the MCP tools. This means:

  1. The MCP server wasn't registered — check container/agent-runner/src/index.ts has the ollama entry in mcpServers
  2. The per-group source wasn't updated — re-copy files (see Phase 2)
  3. The container wasn't rebuilt — run ./container/build.sh

"Failed to connect to Ollama"

  1. Verify Ollama is running: ollama list
  2. Check Docker can reach the host: docker run --rm curlimages/curl curl -s http://host.docker.internal:11434/api/tags
  3. If using a custom host, check OLLAMA_HOST in .env

Agent doesn't use Ollama tools

The agent may not know about the tools. Try being explicit: "use the ollama_generate tool with gemma3:1b to answer: ..."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.