swarmx-doctor

Diagnose SwarmX and Ollama pressure, model residency, and pipeline health with read-only checks.

1|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/sabiscore/the-yap-engine --skill swarmx-doctor-sabiscore
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swarmx-doctor
Source: https://github.com/sabiscore/the-yap-engine/tree/main/integrations/openclaw/skills/swarmx-doctor
Command: npx skills add https://github.com/sabiscore/the-yap-engine --skill swarmx-doctor-sabiscore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a local multi-agent LLM pipeline misbehaves on constrained CPU-only hardware, operators need a safe way to find the root cause without accidentally changing protected production settings. This Skill runs a structured, read-only diagnostic pass over the SwarmX/Ollama stack and returns an incident-style report. ## Core Features & Use Cases - Ten-point health check: Verifies API health, Ollama reachability, /api/ps model residency, available RAM, pressure tier, active 7B model, OLLAMA_NUM_PARALLEL, model registry consistency, recent stage failures, and OpenClaw provider configuration. - Invariant protection: Enforces hard stops so diagnostics never mutate protected values such as RAM_CRITICAL_MB=800, MAX_CONCURRENT_JOBS=1, OLLAMA_NUM_PARALLEL=1, the SINGLE-7B lock, or production promotion gates. - Incident-style reporting: Returns observed values, likely cause, a safe next action, and a rollback/containment path. - Use Case: A video generation stage fails on a 16 GB CPU-only host. Run the diagnostic to confirm whether memory pressure evicted the resident model or whether the OpenClaw provider is misconfigured, then follow the recommended safe remediation. ## Quick Start Ask the assistant to run the swarmx-doctor diagnostic and report why the current pipeline stage is failing.

Frequently Asked Questions about swarmx-doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose Ollama model residency and memory pressure issues?▼

Run a read-only diagnostic that checks /api/ps for resident models, reads available RAM, and identifies the current pressure tier. Comparing observed residency against the expected model registry reveals whether memory pressure evicted a required model.

How to troubleshoot SwarmX pipeline stage failures on CPU-only hardware?▼

Check API health and Ollama reachability first, then review recent stage failures and the active 7B model. On constrained hosts, failures usually trace back to RAM pressure, missing residency, or a misconfigured provider rather than the model itself.

What settings should never be changed when debugging a local LLM pipeline?▼

Protected invariants include RAM_CRITICAL_MB=800, MAX_CONCURRENT_JOBS=1, OLLAMA_NUM_PARALLEL=1, the SINGLE-7B lock, and production promotion gates. Changing these during diagnosis can destabilize memory safety and circuit-breaker behavior.

Why does Ollama report no loaded models after a pipeline failure?▼

Memory pressure can trigger eviction of resident models, leaving /api/ps empty. Verify available RAM and the pressure tier, then reload the expected model according to the host profile rather than raising concurrency limits.

Can this diagnostic modify configuration to fix detected problems?▼

No. The diagnostic is strictly read-only and enforces hard stops against mutating protected invariants. It reports observed values, likely cause, a safe next action, and a rollback path for the operator to execute deliberately.