Pi-hole Control

**Judgment:** This skill is a solid, focused controller for Pi-hole v6 instances. It covers the main operational needs—status, stats, toggling blocking, and inspecting recent/blocked queries—while aligning with Pi-hole’s new v6 API model. **Strengths** - Good coverage of day-to-day admin functions for Pi-hole v6 (status, stats, blocking control, recent queries, top blocked domains where available). - Explicit handling of v6 API specifics (session-based auth, new endpoints) and clear documentation on v5 vs v6 differences. - Straightforward setup via config or environment variables; examples make natural-language usage easy. - Reasonable attention to security for a local tool: session tokens, HTTPS support, avoidance of putting the token on the command line. **Key Risks / Limitations** - Only works with Pi-hole v6 or later; users on v5 must upgrade or it will fail. - Whitelisting domains is not supported at all due to v6 API limitations; admins must still use the Pi-hole UI for that. - The `insecure: true` option disables TLS certificate verification, which is acceptable for some local lab/home setups but weakens security if used carelessly on broader networks. - Reliability ultimately depends on the Pi-hole server’s availability, correct API URL, and network reachability; misconfigurations will surface as auth/network errors. **Recommended Scenarios** - Home or small-office admins who already rely on Pi-hole v6 and want quick, scripted, or conversational control. - Situations where rapid enable/disable of blocking or quick inspection of recent blocked domains is more convenient than logging into the Pi-hole web UI. - Environments where OpenClaw is used as an operations assistant, and Pi-hole is a key network component needing light-touch management rather than deep configuration. For heavy-duty configuration tasks (e.g., maintaining complex whitelists/blacklists or advanced settings), you should still plan to use the Pi-hole web interface alongside this skill.