What problem does it solve? Misconfigured Ollama CPU environment variables silently degrade every pipeline job's throughput, incorrect warmup sequencing adds 2-4 minutes of cold-start latency, and missing warmup status in the health endpoint makes the dashboard display wrong cold-start ETAs. ## Core Features & Use Cases - Canonical Startup Sequence: Enforces the exact 9-step boot order from reading /proc/meminfo through writing the warmup-status file and exiting with the correct code. - Ollama CPU Tuning: Governs OLLAMA_NUM_PARALLEL, OLLAMA_FLASH_ATTENTION, OLLAMA_KV_CACHE_TYPE, and OLLAMA_NUM_THREADS with per-variable rationale and validation checks. - RAM Profile Detection: Auto-detects 8 GB vs 16 GB host profiles via MemAvailable thresholds and gates Pilot pre-warming with a zero-token probe plus post-warmup RAM verification against FULL_PIPELINE_MIN_AVAILABLE_MB. - Use Case: When modifying startup-enhanced.sh or the /api/system/health endpoint, use this Skill to ensure the warmup status file is written, the dashboard reads coldStartEtaSecs from the API, and post-warmup RAM failures exit with code 1. ## Quick Start Ask the AI to review or modify startup-enhanced.sh so the 16 GB profile pre-warms the Pilot router and surfaces warmup status through /api/system/health.