← Back to Skills Marketplace
twinsgeeks

Homelab Ai

by Twin Geeks · GitHub ↗ · v1.0.2 · MIT-0
darwinlinuxwindows ⚠ suspicious
146
Downloads
0
Stars
2
Active Installs
3
Versions
Install in OpenClaw
/install homelab-ai
Description
Home lab AI — turn your spare machines into a local AI home lab cluster. LLM inference, image generation, speech-to-text, and embeddings across macOS, Linux,...
README (SKILL.md)

Home Lab AI — Your Spare Machines Are a Cluster

You have machines sitting around your home lab. A mini PC in the closet. A workstation on the desk. Maybe a desktop doing light work. Together, your home lab has more compute than most cloud instances — you just need software that treats them as one home lab system. Works on macOS, Linux, and Windows.

Ollama Herd turns your home lab into a local AI cluster. One home lab endpoint, zero config, four model types.

What your home lab gets

Device 1 (32GB)    ─┐
Device 2 (64GB)     ├──→  Home Lab Router (:11435)  ←──  Your apps / agents
Device 3 (256GB)   ─┘
  • Home lab LLM inference — Llama, Qwen, DeepSeek, Phi, Mistral, Gemma
  • Home lab image generation — Stable Diffusion 3, Flux, z-image-turbo
  • Home lab speech-to-text — Qwen3-ASR transcription
  • Home lab embeddings — nomic-embed-text, mxbai-embed for RAG

All routed to the best available home lab device automatically.

Home Lab Setup (5 minutes)

On every home lab machine:

pip install ollama-herd    # Home lab AI router

Pick one home lab machine as the router:

herd    # starts the home lab router

On every other home lab machine:

herd-node    # joins the home lab fleet automatically

That's it. Home lab devices discover each other automatically on your local network. No IP addresses, no config files, no Docker, no Kubernetes.

Optional: add home lab image generation

uv tool install mflux           # Flux models (fastest for home labs)
uv tool install diffusionkit    # Stable Diffusion 3/3.5

Use Your Home Lab

Home lab LLM chat

from openai import OpenAI

# Home lab inference client
homelab_client = OpenAI(base_url="http://localhost:11435/v1", api_key="not-needed")
homelab_response = homelab_client.chat.completions.create(
    model="llama3.3:70b",
    messages=[{"role": "user", "content": "How do I set up a home lab NAS?"}],
    stream=True,
)
for chunk in homelab_response:
    print(chunk.choices[0].delta.content or "", end="")

Home lab image generation

curl -o homelab_output.png http://localhost:11435/api/generate-image \
  -H "Content-Type: application/json" \
  -d '{"model": "z-image-turbo", "prompt": "a cozy home lab with servers and RGB lighting", "width": 1024, "height": 1024}'

Home lab transcription

curl http://localhost:11435/api/transcribe -F "file=@homelab_standup.wav" -F "model=qwen3-asr"

Home lab knowledge base

curl http://localhost:11435/api/embed \
  -d '{"model": "nomic-embed-text", "input": "home lab networking and AI inference best practices"}'

How the Home Lab Routes Requests

The home lab router scores each device on 7 signals and picks the best one:

Home Lab Signal What it measures
Thermal state Is the home lab model already loaded (hot) or needs cold-loading?
Memory fit Does the home lab device have enough RAM for this model?
Queue depth Is the home lab device already busy with other requests?
Wait time How long has the home lab request been waiting?
Role affinity Big models prefer big home lab machines, small models prefer small ones
Availability trend Is this home lab device reliably available at this time of day?
Context fit Does the loaded context window fit the home lab request?

You don't manage any of this. The home lab router handles it.

The Home Lab Dashboard

Open http://localhost:11435/dashboard in your browser — your home lab command center:

  • Home Lab Fleet Overview — see every device, loaded models, queue depths, health
  • Trends — home lab requests per hour, latency, token throughput over 24h-7d
  • Health — 15 automated home lab checks with recommendations
  • Recommendations — optimal home lab model mix per device based on your hardware

Recommended Home Lab Models by Device

Cross-platform: These are example configurations. Any device (Mac, Linux, Windows) with equivalent RAM works. The fleet router runs on all platforms.

Home Lab Device RAM Start with
MacBook Air (8GB) 8GB phi4-mini, gemma3:1b
Mac Mini (16GB) 16GB phi4, gemma3:4b, nomic-embed-text
Mac Mini (32GB) 32GB qwen3:14b, deepseek-r1:14b
MacBook Pro (64GB) 64GB qwen3:32b, codestral, z-image-turbo
Mac Studio (128GB) 128GB llama3.3:70b, qwen3:72b
Mac Studio (256GB) 256GB gpt-oss:120b, sd3.5-large

The home lab router's model recommender suggests the optimal mix: GET /dashboard/api/recommendations.

Works with Every Home Lab Tool

The home lab fleet exposes an OpenAI-compatible API. Any tool that works with OpenAI works with your home lab:

Tool Home Lab Connection
Open WebUI Set Ollama URL to http://homelab-router:11435
Aider aider --openai-api-base http://homelab-router:11435/v1
Continue.dev Base URL: http://homelab-router:11435/v1
LangChain ChatOpenAI(base_url="http://homelab-router:11435/v1")
CrewAI Set OPENAI_API_BASE=http://homelab-router:11435/v1
Any OpenAI SDK Base URL: http://homelab-router:11435/v1, API key: any string

Full documentation

Contribute

Ollama Herd is open source (MIT) and built by home lab enthusiasts for home lab enthusiasts:

  • Star on GitHub — help other home lab builders find us
  • Open an issue — share your home lab setup, report bugs
  • PRs welcome — from humans and AI agents. CLAUDE.md gives full context.
  • Built by twin brothers in Alaska who run their own home lab fleet.

Home Lab Guardrails

  • No automatic downloads — home lab model pulls require explicit user confirmation. Some models are 70GB+.
  • Home lab model deletion requires explicit user confirmation.
  • All home lab requests stay local — no data leaves your home network.
  • Never delete or modify files in ~/.fleet-manager/ (home lab routing data and logs).
  • No cloud dependencies — your home lab works offline after initial model downloads.
Usage Guidance
This skill is instruction-only and tells you to 'pip install ollama-herd' and run 'herd'/'herd-node' which will install and run third-party code that opens a local HTTP API and uses mDNS on your LAN. Before installing or running it: 1) inspect the source — visit the GitHub repo and PyPI package (verify maintainers, recent commits, and release artifacts); 2) review the package code (or its wheel) so you know what the daemons do and what files they create (~/.fleet-manager); 3) run the package in an isolated environment (VM or air-gapped machine) or at least inside a non-root virtualenv/container; 4) restrict network exposure — ensure port 11435 and mDNS are only accessible on trusted networks and not forwarded to the Internet; 5) verify the provenance of auxiliary tools mentioned (the 'uv' tool and its install sources); 6) avoid running as root and monitor created processes and outbound network connections on first run. If you want a stronger assurance, request an install spec with verified release URLs or a signed release binary, or ask the publisher for reproducible build and provenance information.
Capability Assessment
Purpose & Capability
The skill claims to set up a local AI cluster and the SKILL.md shows the expected steps (pip install ollama-herd, run herd/herd-node, expose a local OpenAI-compatible API on :11435). However, the metadata's declared binary requirements (anyBins: curl|wget, optionalBins: python3|pip) do not mention the runtime binaries the instructions actually use (herd, herd-node, uv, uv tool). That's a discrepancy (missing declared runtime binaries) but not necessarily malicious — it makes the documentation/manifest incomplete and surprises users about what will run.
Instruction Scope
Instructions direct the user to install a PyPI package and run daemons that advertise via mDNS and expose an HTTP API on the LAN. All of that is within the claimed purpose (local cluster), but it will cause new services to listen on the network and write to local config paths (~/.fleet-manager). The instructions do not request unrelated files or credentials, and they don't explicitly exfiltrate data — but running unreviewed packages and enabling mDNS/network endpoints expands attack surface and warrants caution.
Install Mechanism
There is no platform-level install spec; the runtime instructions tell users to run 'pip install ollama-herd' and to use 'uv tool install', which will pull code from external package sources (PyPI and whatever 'uv' uses). Installing third-party packages from external registries and running their daemons is a moderate-to-high risk action because it executes arbitrary remote code and may drop files/configs. The skill metadata does not provide an audited release URL or pinned provenance for these artifacts.
Credentials
The skill declares no required environment variables and the instructions don't ask for credentials. The config paths in metadata (~/.fleet-manager/...) match the described runtime behavior (local router state/logs). Requested access seems proportional to the purpose (local service state), not excessive.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges in the registry metadata. It will create local config/log files and run local daemons, which is expected for a router service, but it does not attempt to modify other skills or global agent settings according to the provided manifest.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install homelab-ai
  3. After installation, invoke the skill by name or use /homelab-ai
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
Cross-platform support: macOS, Linux, and Windows. Updated OS metadata, descriptions, and hardware recommendations.
v1.0.1
- Documentation rewritten to consistently use "home lab" language throughout, clarifying the scope and intended use of the skill. - Expanded multi-language description (Chinese and Spanish) added for broader accessibility. - All user/documentation example commands, explanations, and table headings updated to reference "home lab" contexts and terminology. - No changes to underlying code or features: this update is entirely documentation/README focused.
v1.0.0
Initial release of homelab-ai — easily turn spare Macs into a local AI cluster. - Combine Mac Studio, Mac Mini, MacBook Pro, and Mac Pro into one AI fleet with no configuration. - Supports LLM inference (Llama, Qwen, DeepSeek, etc.), image generation (Stable Diffusion, Flux), speech-to-text, and embeddings. - Simple setup: install on each Mac, run one as the router, others as nodes; devices discover each other automatically. - Real-time dashboard provides fleet health, trends, recommendations, and device status. - OpenAI-compatible API; works with popular tools and libraries. - No cloud, Docker, or Kubernetes required; all computation and data stay local.
Metadata
Slug homelab-ai
Version 1.0.2
License MIT-0
All-time Installs 2
Active Installs 2
Total Versions 3
Frequently Asked Questions

What is Homelab Ai?

Home lab AI — turn your spare machines into a local AI home lab cluster. LLM inference, image generation, speech-to-text, and embeddings across macOS, Linux,... It is an AI Agent Skill for Claude Code / OpenClaw, with 146 downloads so far.

How do I install Homelab Ai?

Run "/install homelab-ai" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Homelab Ai free?

Yes, Homelab Ai is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Homelab Ai support?

Homelab Ai is cross-platform and runs anywhere OpenClaw / Claude Code is available (darwin, linux, windows).

Who created Homelab Ai?

It is built and maintained by Twin Geeks (@twinsgeeks); the current version is v1.0.2.

💬 Comments