Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Control Pi-hole v6 DNS ad blocker: check status, view stats, enable/disable block, and analyze blocked domains via API.
Control Pi-hole v6 DNS ad blocker: check status, view stats, enable/disable block, and analyze blocked domains via API.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Control your Pi-hole DNS ad blocker via the Pi-hole v6 API.
Set your Pi-hole API configuration in Clawdbot config: skills: entries: pihole: apiUrl: "https://pi-hole.local/api" # v6 API path apiToken: "your-app-password-here" # Get from Pi-hole Admin insecure: false # Set to true for self-signed certs Alternatively, set environment variables: export PIHOLE_API_URL="https://pi-hole.local/api" export PIHOLE_API_TOKEN="your-app-password-here" export PIHOLE_INSECURE="false"
Open Pi-hole Admin at http://pi-hole.local/admin Navigate to Settings > API Generate an app password Use that password as apiToken
Get current Pi-hole status (enabled/disabled) View stats: queries blocked, queries today, domains being blocked, active clients See recent query activity
Enable/Disable: Turn Pi-hole on or off Disable for 5 minutes: Temporarily disable ad blocking for a short period Disable for custom duration: Set specific disable time (in minutes)
Check blocked domains: See what domains were blocked in a time window Show top blocked: Most frequently blocked domains
# Check Pi-hole status "pihole status" # Turn off ad blocking "pihole off" # Turn on ad blocking "pihole on" # Disable for 5 minutes (for a site that needs ads) "pihole disable 5m" # Disable for 30 minutes "pihole disable 30" # See what was blocked in the last 30 minutes "pihole blocked" # See blocked domains in last 10 minutes (600 seconds) "pihole blocked 600" # Show statistics "pihole stats"
POST /api/auth Content-Type: application/json {"password":"your-app-password"} Response: { "session": { "sid": "session-token-here", "validity": 1800 } }
GET /api/dns/blocking Headers: sid: <session-token> Response: { "blocking": "enabled" | "disabled", "timer": 30 // seconds until re-enable (if disabled with timer) }
POST /api/dns/blocking Headers: sid: <session-token> Content-Type: application/json Enable: {"blocking":true} Disable: {"blocking":false} Disable with timer (seconds): {"blocking":false,"timer":300}
GET /api/stats/summary Headers: sid: <session-token> Response: { "queries": { "total": 233512, "blocked": 23496, "percent_blocked": 10.06 }, "gravity": { "domains_being_blocked": 165606 }, "clients": { "active": 45 } }
GET /api/queries?start=-<seconds> Headers: sid: <session-token> Response: { "queries": [ { "domain": "example.com", "status": "GRAVITY", "time": 1768363900, "type": "A" } ] }
Pi-hole v6 introduced significant API changes: Featurev5 APIv6 APIBase URL/admin/api.php/apiAuthToken in URL/headersSession-basedStatus?status/api/dns/blockingStats?summaryRaw/api/stats/summaryQueries?recentBlocked/api/queriesWhitelistSupported via APINot available via API Important: Domain whitelisting is no longer available via the v6 API. You must whitelist domains through the Pi-hole Admin UI.
{ "apiUrl": "https://pi-hole.example.com/api", "apiToken": "...", "insecure": false }
{ "apiUrl": "https://pi-hole.local/api", "apiToken": "...", "insecure": true } The insecure flag adds the -k option to curl to bypass certificate validation.
Session tokens expire after 30 minutes (1800 seconds) API password is sent in JSON body, not URL All requests have a 30-second timeout Token is not visible in process list (passed via environment)
Check that apiToken matches your Pi-hole app password Verify apiUrl is correct (must end in /api) Ensure Pi-hole is accessible from your network
Check API URL is reachable If using HTTPS with self-signed cert, set insecure: true Verify API password is correct
Ensure clawdbot's machine can reach the Pi-hole Check firewall rules allow API access Verify URL scheme (http vs https)
Pi-hole v6 or later App password generated in Pi-hole Admin Network access to Pi-hole API curl, jq (installed on most Unix systems)
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.