Homelab Network Readiness

Before you carve your flat home network into VLANs, point everyone at Pi-hole, or open a WireGuard port, this skill walks you through inventory, staged planning, and rollback prep so you don't lock yourself out of your own gateway. It's deliberately read-only at first: you answer questions about your modem, switch ports, SSIDs, and subnets before it suggests any commands. The safety rules are practical, like keeping console access before changing management VLANs and testing DNS on one client before flipping every DHCP scope. Use it when you're past the "I should segment my IoT devices" idea stage and need a checklist that respects the fact that your router, Pi-hole, and VPN all need to stay reachable.

skills.sh installs: 5.4K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill homelab-network-readiness --agent claude-code

Installs into .claude/skills of the current project.

Files

Homelab Network Readiness

Use this skill before changing a home or small-lab network that mixes VLANs, Pi-hole or another local DNS resolver, firewall rules, and remote VPN access.

This is a planning and review skill. Do not turn it into copy-paste router, firewall, or VPN configuration unless the target platform, current topology, rollback path, console access, and maintenance window are all known.

When to Use

Preparing to split a flat network into trusted, IoT, guest, server, or management VLANs.
Moving DHCP clients to Pi-hole, AdGuard Home, Unbound, or another local DNS resolver.
Adding WireGuard, Tailscale, ZeroTier, OpenVPN, or router-native VPN access.
Reviewing whether a homelab change can lock the operator out of the gateway, switch, access point, DNS server, or VPN server.
Turning an informal home-network idea into a staged migration plan with validation evidence.