pihole
Skill0 starsChanged 4 days agoMITView on GitHub
Pi-hole DNS sinkhole management. Use when: user asks about ad blocking status, DNS queries, blocked domains, allowlists/denylists, network devices, or DHCP leases. Controls the local Pi-hole v6 instance via REST API.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- codex-model-profilesSkill
- cognitive-rhythm-writingSkill
- daikinSkill
- decoSkill
- epgstationSkill
- japanese-tech-writingSkill
- popin-aladdinSkill
- stirling-pdfSkill
- switch2-controlSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
When disabling blocking, always pass a timer (seconds) unless the user explicitly wants it disabled indefinitely — warn them either way.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pi-hole
Base URL: https://pihole.msageha.net/api (Pi-hole v6 REST API). Requests to
this instance don't need any authentication header/cookie. The reverse proxy
only admits allowlisted LAN client IPs — a 403 with an nginx HTML page means
the caller isn't on that list, not an API error.
Key facts
- Session-based SID auth exists for password-protected instances (
POST /auth, header/query/cookiesid) but isn't needed for this instance. - When disabling blocking, always pass a
timer(seconds) unless the user explicitly wants it disabled indefinitely — warn them either way. - Confirm with the user before modifying allow/deny lists, adding adlists, or running a gravity update (gravity update can take a while).
Core operations
| Task | Endpoint |
| Status summary | GET /stats/summary |
| Blocking on/off | GET/POST /dns/blocking |
| Recent / top blocked domains | GET /stats/recent_blocked, GET /stats/top_domains |
| Query log | GET /queries |
| Search a domain | GET /search/{domain} |
| Allow / deny a domain | POST /domains/{type}/{kind} |
| List / remove domains | GET /domains, DELETE /domains/{type}/{kind}/{domain} |
| Network devices | GET /network/devices |
| DHCP leases | GET /dhcp/leases |
| Adlists | GET/POST /lists |
| Update gravity / restart DNS | POST /action/gravity, POST /action/restartdns |
| Version / system info | GET /info/version, GET /info/system |
Full request/response schemas and ready-to-run curl examples: see references/api-reference.md and references/commands.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.