[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78CYWMK00BFXT422VGX9EQC":3,"skill-same:01M78CYWMK00BFXT422VGX9EQC":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M78CYWMK00BFXT422VGX9EQC","homelab-pihole-dns",null,"Pi-hole installation, blocklist management, DNS-over-HTTPS setup, DHCP integration, local DNS records, and troubleshooting broken DNS resolution on a home network.","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fhomelab-pihole-dns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: homelab-pihole-dns\ndescription: Pi-hole installation, blocklist management, DNS-over-HTTPS setup, DHCP integration, local DNS records, and troubleshooting broken DNS resolution on a home network.\norigin: community\n---\n\n# Homelab Pi-hole DNS\n\nPi-hole is a network-wide DNS ad blocker that runs on a Raspberry Pi or any Linux host.\nEvery device on your network gets ad and malware domain blocking automatically — no browser\nextension needed.\n\n## When to Use\n\n- Installing Pi-hole on a Raspberry Pi or Linux host\n- Configuring Pi-hole as the DNS server for a home network\n- Adding or managing blocklists\n- Setting up DNS-over-HTTPS (DoH) upstream resolvers\n- Creating local DNS records (e.g. `nas.home.lan`, `pi.home.lan`)\n- Troubleshooting devices that lose internet access after Pi-hole is installed\n- Running Pi-hole alongside or instead of DHCP\n\n## How Pi-hole Works\n\n```\nNormal flow (without Pi-hole):\n  Device → requests ads.tracker.com → ISP DNS → real IP → ads load\n\nWith Pi-hole:\n  Device → requests ads.tracker.com → Pi-hole DNS → blocked (returns 0.0.0.0) → no ad\n\nAll DNS queries go through Pi-hole first.\nPi-hole checks against blocklists.\nBlocked domains return a null response — the ad\u002Ftracker never loads.\nAllowed domains get forwarded to your upstream resolver (Cloudflare, Google, etc.).\n```\n\n## Installation\n\n### Docker (Recommended)\n\nDocker is the easiest way to install Pi-hole and makes updates and backups\nstraightforward.\n\n```yaml\n# docker-compose.yml\nservices:\n  pihole:\n    image: pihole\u002Fpihole:\u003Cpinned-release-tag>\n    container_name: pihole\n    ports:\n      - \"53:53\u002Ftcp\"\n      - \"53:53\u002Fudp\"\n      - \"80:80\u002Ftcp\"          # Web admin\n    environment:\n      TZ: \"America\u002FNew_York\"\n      WEBPASSWORD: \"${PIHOLE_WEBPASSWORD}\"   # set via .env file or secret\n      PIHOLE_DNS_: \"1.1.1.1;1.0.0.1\"\n      DNSMASQ_LISTENING: \"all\"\n    volumes:\n      - \".\u002Fetc-pihole:\u002Fetc\u002Fpihole\"\n      - \".\u002Fetc-dnsmasq.d:\u002Fetc\u002Fdnsmasq.d\"\n    restart: unless-stopped\n    cap_add:\n      - NET_ADMIN              # only needed if Pi-hole will serve DHCP\n```\n\nReplace `\u003Cpinned-release-tag>` with a current Pi-hole release tag before deploying.\nAvoid `latest` for long-lived DNS infrastructure so upgrades are deliberate and\nreviewable.\n\nSet `PIHOLE_WEBPASSWORD` in a `.env` file next to `docker-compose.yml`, chmod it to\n`600`, and keep it out of git — do not put the password directly in the compose file.\n\nAccess web admin at: `http:\u002F\u002F\u003Cpi-ip>\u002Fadmin`\n\n### Bare-Metal Install (Raspberry Pi OS \u002F Debian \u002F Ubuntu)\n\nPi-hole requires a static IP before installing.\n\n```bash\n# Step 1: Assign a static IP (edit \u002Fetc\u002Fdhcpcd.conf on Pi OS)\nsudo nano \u002Fetc\u002Fdhcpcd.conf\n# Add at the bottom:\ninterface eth0\nstatic ip_address=192.168.3.2\u002F24\nstatic routers=192.168.3.1\nstatic domain_name_servers=192.168.3.1\n\n# Step 2: Download and inspect the installer before running it.\n# Prefer the package or installer path documented by Pi-hole for your OS\u002Fversion.\ncurl -sSL https:\u002F\u002Finstall.pi-hole.net -o pi-hole-install.sh\nless pi-hole-install.sh   # review before proceeding\n\n# Step 3: Run\nbash pi-hole-install.sh\n\n# Follow the interactive installer:\n#   1. Select network interface (eth0 for wired — recommended)\n#   2. Select upstream DNS (Cloudflare or leave default — can change later)\n#   3. Confirm static IP\n#   4. Install the web admin interface (recommended)\n#   5. Note the admin password shown at the end\n```\n\n## Pointing Your Network at Pi-hole\n\n```\n# Method 1: Change DNS in your router DHCP settings (recommended)\n  Router admin UI → DHCP Settings → DNS Server\n  Primary DNS: 192.168.3.2  (Pi-hole IP)\n  Secondary DNS: leave blank for strict blocking, or use a second Pi-hole.\n                 A public fallback such as 1.1.1.1 improves availability during\n                 rollout but can bypass blocking because clients may query it.\n\n  All devices get Pi-hole as DNS automatically on next DHCP renewal.\n  Force renewal: reconnect Wi-Fi or run 'sudo dhclient -r && sudo dhclient' on Linux\n\n# Method 2: Per-device DNS (useful for testing before network-wide rollout)\n  Windows: Control Panel → Network Adapter → IPv4 Properties → set DNS manually\n  macOS: System Settings → Network → Details → DNS → set manually\n  Linux: \u002Fetc\u002Fresolv.conf or NetworkManager\n\n# Method 3: Pi-hole as DHCP server (replaces router DHCP)\n  Pi-hole admin → Settings → DHCP → Enable\n  Disable DHCP on your router first — two DHCP servers on the same network cause conflicts\n  Advantage: hostname resolution works automatically (devices register their names)\n```\n\n## Blocklist Management\n\n```\n# Pi-hole admin → Adlists → Add new adlist\n\n# Recommended blocklists:\n  https:\u002F\u002Fraw.githubusercontent.com\u002FStevenBlack\u002Fhosts\u002Fmaster\u002Fhosts\n  # default — 200k+ domains\n\n  https:\u002F\u002Fblocklistproject.github.io\u002FLists\u002Fmalware.txt\n  # malware domains\n\n  https:\u002F\u002Fblocklistproject.github.io\u002FLists\u002Ftracking.txt\n  # tracking\u002Ftelemetry\n\n# After adding a list:\n  Tools → Update Gravity  (downloads and compiles all blocklists)\n\n# If a site is blocked that should not be (false positive):\n  Pi-hole admin → Whitelist → Add domain\n  Example: api.my-legitimate-service.com\n\n# Check what is being blocked in real time:\n  Dashboard → Query Log  (live DNS query stream with block\u002Fallow status)\n```\n\n## DNS-over-HTTPS Upstream\n\nDNS-over-HTTPS encrypts your DNS queries so your ISP cannot see what sites you resolve.\n\n```bash\n# Install cloudflared (Cloudflare's DoH proxy).\n# Prefer Cloudflare's package repository for automatic signed package verification.\n# If you download a binary directly, pin a release version and verify its checksum.\nCLOUDFLARED_VERSION=\"\u003Cpinned-version>\"\ncurl -LO \"https:\u002F\u002Fgithub.com\u002Fcloudflare\u002Fcloudflared\u002Freleases\u002Fdownload\u002F${CLOUDFLARED_VERSION}\u002Fcloudflared-linux-arm64\"\n# Verify the checksum\u002Fsignature from Cloudflare's release notes before installing.\nsudo mv cloudflared-linux-arm64 \u002Fusr\u002Flocal\u002Fbin\u002Fcloudflared\nsudo chmod +x \u002Fusr\u002Flocal\u002Fbin\u002Fcloudflared\n\n# Create cloudflared config\nsudo mkdir -p \u002Fetc\u002Fcloudflared\nsudo tee \u002Fetc\u002Fcloudflared\u002Fconfig.yml \u003C\u003C EOF\nproxy-dns: true\nproxy-dns-port: 5053\nproxy-dns-upstream:\n  - https:\u002F\u002F1.1.1.1\u002Fdns-query\n  - https:\u002F\u002F1.0.0.1\u002Fdns-query\nEOF\n\n# Create systemd service\nsudo cloudflared service install\nsudo systemctl start cloudflared\nsudo systemctl enable cloudflared\n\n# Now point Pi-hole at the local DoH proxy:\n#   Pi-hole admin → Settings → DNS → Custom upstream DNS\n#   Set to: 127.0.0.1#5053\n#   Uncheck all other upstream resolvers\n```\n\n## Local DNS Records\n\nMake your services reachable by name (e.g. `nas.home.lan`, `grafana.home.lan`).\n\n> **Domain name note:** `.home.lan` is widely used in homelabs and works in practice.\n> The IETF-reserved suffix for local use is `.home.arpa` (RFC 8375) — use that to\n> follow the standard. Avoid `.local` for Pi-hole DNS records as it conflicts with\n> mDNS\u002FBonjour.\n\n```\n# Pi-hole admin → Local DNS → DNS Records\n\n  Domain              IP\n  nas.home.lan        192.168.30.10\n  pi.home.lan         192.168.30.2\n  grafana.home.lan    192.168.30.3\n  proxmox.home.lan    192.168.30.4\n\n# From any device on your network:\n  ping nas.home.lan        → 192.168.30.10\n  http:\u002F\u002Fgrafana.home.lan  → your Grafana dashboard\n\n# For subdomains, add a CNAME:\n  Pi-hole admin → Local DNS → CNAME Records\n  Domain: portainer.home.lan → Target: pi.home.lan\n```\n\n## Troubleshooting\n\n```bash\n# Pi-hole blocking something it should not\npihole -q example.com          # Check if domain is blocked and which list\npihole -w example.com          # Whitelist immediately\n\n# DNS not resolving at all\npihole status                  # Check if pihole-FTL is running\ndig @192.168.3.2 google.com   # Test DNS directly against Pi-hole\n\n# Restart Pi-hole DNS\npihole restartdns\n\n# Check query logs for a specific device\npihole -t                      # Live tail of all queries\n# Or filter by client in the web admin Query Log\n\n# Pi-hole gravity update (refresh blocklists)\npihole -g\n```\n\n## Anti-Patterns\n\n```\n# BAD: Depending on one Pi-hole without a recovery path\n# If Pi-hole crashes or the Pi loses power, DNS can stop working\n# GOOD: Keep a documented router fallback for rollback during setup\n# BETTER: Run two Pi-hole instances for redundancy; avoid public fallback DNS for strict blocking\n\n# BAD: Installing Pi-hole without a static IP\n# If the Pi gets a new DHCP IP, all devices lose DNS\n# GOOD: Set static IP first, then install Pi-hole\n\n# BAD: Enabling Pi-hole DHCP without disabling the router's DHCP first\n# Two DHCP servers on the same network hand out conflicting IPs\n# GOOD: Disable router DHCP, then enable Pi-hole DHCP\n\n# BAD: Never updating gravity (blocklists)\n# New ad and malware domains accumulate — stale lists miss them\n# GOOD: Schedule weekly gravity update: pihole -g (or enable in Settings → API)\n```\n\n## Best Practices\n\n- Give the Pi a static IP or DHCP reservation before installing Pi-hole\n- Use Pi-hole as primary DNS; for redundancy, add a second Pi-hole instead of a\n  public resolver if you need strict blocking\n- Enable DoH (DNS-over-HTTPS) with cloudflared for encrypted upstream queries\n- Set `home.lan` as your local domain and create DNS records for all your services\n- Review the Query Log occasionally — blocked queries show you what devices are doing\n\n## Related Skills\n\n- homelab-network-setup\n- homelab-vlan-segmentation\n- homelab-wireguard-vpn\n","# Homelab Pi-hole DNS\n\nPi-hole is a network-wide DNS ad blocker that runs on a Raspberry Pi or any Linux host.\nEvery device on your network gets ad and malware domain blocking automatically — no browser\nextension needed.\n\n## When to Use\n\n- Installing Pi-hole on a Raspberry Pi or Linux host\n- Configuring Pi-hole as the DNS server for a home network\n- Adding or managing blocklists\n- Setting up DNS-over-HTTPS (DoH) upstream resolvers\n- Creating local DNS records (e.g. `nas.home.lan`, `pi.home.lan`)\n- Troubleshooting devices that lose internet access after Pi-hole is installed\n- Running Pi-hole alongside or instead of DHCP\n\n## How Pi-hole Works\n\n```\nNormal flow (without Pi-hole):\n  Device → requests ads.tracker.com → ISP DNS → real IP → ads load\n\nWith Pi-hole:\n  Device → requests ads.tracker.com → Pi-hole DNS → blocked (returns 0.0.0.0) → no ad\n\nAll DNS queries go through Pi-hole first.\nPi-hole checks against blocklists.\nBlocked domains return a null response — the ad\u002Ftracker never loads.\nAllowed domains get forwarded to your upstream resolver (Cloudflare, Google, etc.).\n```\n\n## Installation\n\n### Docker (Recommended)\n\nDocker is the easiest way to install Pi-hole and makes updates and backups\nstraightforward.\n\n```yaml\n# docker-compose.yml\nservices:\n  pihole:\n    image: pihole\u002Fpihole:\u003Cpinned-release-tag>\n    container_name: pihole\n    ports:\n      - \"53:53\u002Ftcp\"\n      - \"53:53\u002Fudp\"\n      - \"80:80\u002Ftcp\"          # Web admin\n    environment:\n      TZ: \"America\u002FNew_York\"\n      WEBPASSWORD: \"${PIHOLE_WEBPASSWORD}\"   # set via .env file or secret\n      PIHOLE_DNS_: \"1.1.1.1;1.0.0.1\"\n      DNSMASQ_LISTENING: \"all\"\n    volumes:\n      - \".\u002Fetc-pihole:\u002Fetc\u002Fpihole\"\n      - \".\u002Fetc-dnsmasq.d:\u002Fetc\u002Fdnsmasq.d\"\n    restart: unless-stopped\n    cap_add:\n      - NET_ADMIN              # only needed if Pi-hole will serve DHCP\n```\n\nReplace `\u003Cpinned-release-tag>` with a current Pi-hole release tag before deploying.\nAvoid `latest` for long-lived DNS infrastructure so upgrades are deliberate and\nreviewable.\n\nSet `PIHOLE_WEBPASSWORD` in a `.env` file next to `docker-compose.yml`, chmod it to\n`600`, and keep it out of git — do not put the password directly in the compose file.\n\nAccess web admin at: `http:\u002F\u002F\u003Cpi-ip>\u002Fadmin`\n\n### Bare-Metal Install (Raspberry Pi OS \u002F Debian \u002F Ubuntu)\n\nPi-hole requires a static IP before installing.\n\n```bash\n# Step 1: Assign a static IP (edit \u002Fetc\u002Fdhcpcd.conf on Pi OS)\nsudo nano \u002Fetc\u002Fdhcpcd.conf\n# Add at the bottom:\ninterface eth0\nstatic ip_address=192.168.3.2\u002F24\nstatic routers=192.168.3.1\nstatic domain_name_servers=192.168.3.1\n\n# Step 2: Download and inspect the installer before running it.\n# Prefer the package or installer path documented by Pi-hole for your OS\u002Fversion.\ncurl -sSL https:\u002F\u002Finstall.pi-hole.net -o pi-hole-install.sh\nless pi-hole-install.sh   # review before proceeding\n\n# Step 3: Run\nbash pi-hole-install.sh\n\n# Follow the interactive installer:\n#   1. Select network interface (eth0 for wired — recommended)\n#   2. Select upstream DNS (Cloudflare or leave default — can change later)\n#   3. Confirm static IP\n#   4. Install the web admin interface (recommended)\n#   5. Note the admin password shown at the end\n```\n\n## Pointing Your Network at Pi-hole\n\n```\n# Method 1: Change DNS in your router DHCP settings (recommended)\n  Router admin UI → DHCP Settings → DNS Server\n  Primary DNS: 192.168.3.2  (Pi-hole IP)\n  Secondary DNS: leave blank for strict blocking, or use a second Pi-hole.\n                 A public fallback such as 1.1.1.1 improves availability during\n                 rollout but can bypass blocking because clients may query it.\n\n  All devices get Pi-hole as DNS automatically on next DHCP renewal.\n  Force renewal: reconnect Wi-Fi or run 'sudo dhclient -r && sudo dhclient' on Linux\n\n# Method 2: Per-device DNS (useful for testing before network-wide rollout)\n  Windows: Control Panel → Network Adapter → IPv4 Properties → set DNS manually\n  macOS: System Settings → Network → Details → DNS → set manually\n  Linux: \u002Fetc\u002Fresolv.conf or NetworkManager\n\n# Method 3: Pi-hole as DHCP server (replaces router DHCP)\n  Pi-hole admin → Settings → DHCP → Enable\n  Disable DHCP on your router first — two DHCP servers on the same network cause conflicts\n  Advantage: hostname resolution works automatically (devices register their names)\n```\n\n## Blocklist Management\n\n```\n# Pi-hole admin → Adlists → Add new adlist\n\n# Recommended blocklists:\n  https:\u002F\u002Fraw.githubusercontent.com\u002FStevenBlack\u002Fhosts\u002Fmaster\u002Fhosts\n  # default — 200k+ domains\n\n  https:\u002F\u002Fblocklistproject.github.io\u002FLists\u002Fmalware.txt\n  # malware domains\n\n  https:\u002F\u002Fblocklistproject.github.io\u002FLists\u002Ftracking.txt\n  # tracking\u002Ftelemetry\n\n# After adding a list:\n  Tools → Update Gravity  (downloads and compiles all blocklists)\n\n# If a site is blocked that should not be (false positive):\n  Pi-hole admin → Whitelist → Add domain\n  Example: api.my-legitimate-service.com\n\n# Check what is being blocked in real time:\n  Dashboard → Query Log  (live DNS query stream with block\u002Fallow status)\n```\n\n## DNS-over-HTTPS Upstream\n\nDNS-over-HTTPS encrypts your DNS queries so your ISP cannot see what sites you resolve.\n\n```bash\n# Install cloudflared (Cloudflare's DoH proxy).\n# Prefer Cloudflare's package repository for automatic signed package verification.\n# If you download a binary directly, pin a release version and verify its checksum.\nCLOUDFLARED_VERSION=\"\u003Cpinned-version>\"\ncurl -LO \"https:\u002F\u002Fgithub.com\u002Fcloudflare\u002Fcloudflared\u002Freleases\u002Fdownload\u002F${CLOUDFLARED_VERSION}\u002Fcloudflared-linux-arm64\"\n# Verify the checksum\u002Fsignature from Cloudflare's release notes before installing.\nsudo mv cloudflared-linux-arm64 \u002Fusr\u002Flocal\u002Fbin\u002Fcloudflared\nsudo chmod +x \u002Fusr\u002Flocal\u002Fbin\u002Fcloudflared\n\n# Create cloudflared config\nsudo mkdir -p \u002Fetc\u002Fcloudflared\nsudo tee \u002Fetc\u002Fcloudflared\u002Fconfig.yml \u003C\u003C EOF\nproxy-dns: true\nproxy-dns-port: 5053\nproxy-dns-upstream:\n  - https:\u002F\u002F1.1.1.1\u002Fdns-query\n  - https:\u002F\u002F1.0.0.1\u002Fdns-query\nEOF\n\n# Create systemd service\nsudo cloudflared service install\nsudo systemctl start cloudflared\nsudo systemctl enable cloudflared\n\n# Now point Pi-hole at the local DoH proxy:\n#   Pi-hole admin → Settings → DNS → Custom upstream DNS\n#   Set to: 127.0.0.1#5053\n#   Uncheck all other upstream resolvers\n```\n\n## Local DNS Records\n\nMake your services reachable by name (e.g. `nas.home.lan`, `grafana.home.lan`).\n\n> **Domain name note:** `.home.lan` is widely used in homelabs and works in practice.\n> The IETF-reserved suffix for local use is `.home.arpa` (RFC 8375) — use that to\n> follow the standard. Avoid `.local` for Pi-hole DNS records as it conflicts with\n> mDNS\u002FBonjour.\n\n```\n# Pi-hole admin → Local DNS → DNS Records\n\n  Domain              IP\n  nas.home.lan        192.168.30.10\n  pi.home.lan         192.168.30.2\n  grafana.home.lan    192.168.30.3\n  proxmox.home.lan    192.168.30.4\n\n# From any device on your network:\n  ping nas.home.lan        → 192.168.30.10\n  http:\u002F\u002Fgrafana.home.lan  → your Grafana dashboard\n\n# For subdomains, add a CNAME:\n  Pi-hole admin → Local DNS → CNAME Records\n  Domain: portainer.home.lan → Target: pi.home.lan\n```\n\n## Troubleshooting\n\n```bash\n# Pi-hole blocking something it should not\npihole -q example.com          # Check if domain is blocked and which list\npihole -w example.com          # Whitelist immediately\n\n# DNS not resolving at all\npihole status                  # Check if pihole-FTL is running\ndig @192.168.3.2 google.com   # Test DNS directly against Pi-hole\n\n# Restart Pi-hole DNS\npihole restartdns\n\n# Check query logs for a specific device\npihole -t                      # Live tail of all queries\n# Or filter by client in the web admin Query Log\n\n# Pi-hole gravity update (refresh blocklists)\npihole -g\n```\n\n## Anti-Patterns\n\n```\n# BAD: Depending on one Pi-hole without a recovery path\n# If Pi-hole crashes or the Pi loses power, DNS can stop working\n# GOOD: Keep a documented router fallback for rollback during setup\n# BETTER: Run two Pi-hole instances for redundancy; avoid public fallback DNS for strict blocking\n\n# BAD: Installing Pi-hole without a static IP\n# If the Pi gets a new DHCP IP, all devices lose DNS\n# GOOD: Set static IP first, then install Pi-hole\n\n# BAD: Enabling Pi-hole DHCP without disabling the router's DHCP first\n# Two DHCP servers on the same network hand out conflicting IPs\n# GOOD: Disable router DHCP, then enable Pi-hole DHCP\n\n# BAD: Never updating gravity (blocklists)\n# New ad and malware domains accumulate — stale lists miss them\n# GOOD: Schedule weekly gravity update: pihole -g (or enable in Settings → API)\n```\n\n## Best Practices\n\n- Give the Pi a static IP or DHCP reservation before installing Pi-hole\n- Use Pi-hole as primary DNS; for redundancy, add a second Pi-hole instead of a\n  public resolver if you need strict blocking\n- Enable DoH (DNS-over-HTTPS) with cloudflared for encrypted upstream queries\n- Set `home.lan` as your local domain and create DNS records for all your services\n- Review the Query Log occasionally — blocked queries show you what devices are doing\n\n## Related Skills\n\n- homelab-network-setup\n- homelab-vlan-segmentation\n- homelab-wireguard-vpn\n",{"name":5,"origin":24,"description":7},"community","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fhomelab-pihole-dns","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill homelab-pihole-dns",{"tool":38,"command":39},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill homelab-pihole-dns",{"tool":41,"command":42},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill homelab-pihole-dns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fhomelab-pihole-dns\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]