What problem does it solve? Running conversational Discord bots as always-on launchd services on a Mac mini fails in non-obvious ways: low power mode silently blocks KeepAlive restarts, CLAUDE.md files from parent directories inflate every Claude CLI call with hundreds of kilobytes of context, and launchd's minimal PATH kills node-based CLI fallbacks like Codex. This Skill documents those traps and the exact commands to diagnose and fix them. ## Core Features & Use Cases - Fleet Operations: Check status, restart, and read logs for three resident Discord bots (knowledge-bot-a, daily-brief-agent, bamnyangi) via SSH and launchctl. - Failure Diagnosis: Explains why low power mode pends nondemand spawns, why CLAUDE.md auto-loading inflates token usage, and why rc=127 node errors kill CLI fallbacks without throwing exceptions. - New Bot Creation: Copy an existing bot skeleton (bot.py, answer.py, store.py, persona.md, memory.md) with two-layer short/long-term memory and loop-prevention rules. - Use Case: A user says "the bot stopped answering" — the Skill guides checking launchctl state, using launchctl kickstart -k instead of bootstrap, and verifying PATH in a reproduced launchd environment. ## Quick Start Ask the agent to check why the Discord bot on the Mac mini is not responding and restart it using the launchctl kickstart procedure.