[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVDFKD6VADZ3WR4EYGQWN1":3,"skill-same:01M7CVDFKD6VADZ3WR4EYGQWN1":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CVDFKD6VADZ3WR4EYGQWN1","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.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fdevops-cloud\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.\nmetadata:\n  origin: 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,"metadata":24,"description":7},{"origin":25},"community","main","a73152352c0612252131e5cf84e91312a6cf17dc","devops-cloud\u002Fhomelab-pihole-dns","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill homelab-pihole-dns",{"tool":40,"command":41},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill homelab-pihole-dns",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill homelab-pihole-dns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fdevops-cloud\u002Fhomelab-pihole-dns\u002FSKILL.md",true,[],[49,56,63,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]