affaan-m/ecc/homelab-network-readiness
Claude Code and agent skill by affaan-m/ecc
- community
Checking that the SKILL.md file is still in the repository.
Readiness checklist for homelab VLAN segmentation, local DNS filtering (Pi-hole, AdGuard Home), and WireGuard-style remote access. Use when planning or reviewing home network changes — splitting a flat network into trusted, IoT, guest, or management VLANs, moving DHCP to a local resolver, or adding VPN access — before changing router, firewall, DHCP, or VPN configuration.
Install
npx vskill@latest install affaan-m/ecc/homelab-network-readinessSKILL.md
The same SKILL.md was published earlier as affaan-m/ecc/homelab-network-readiness.
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.
Safety Rules
- Keep the first answer read-only: inventory, risks, staged plan, validation,
and rollback.
- Do not expose gateway admin panels, DNS resolvers, SSH, NAS consoles, or VPN
management UIs directly to the public internet.
- Do not provide firewall, NAT, VLAN, DHCP, or VPN commands without a confirmed
platform and a rollback procedure.
- Require out-of-band or same-room console access before changing management
VLANs, trunk ports, firewall default policies, or DHCP/DNS settings.
- Keep a working path back to the internet before pointing the whole network at
a new DNS resolver or VPN route.
- Treat IoT, guest, camera, and lab-server networks as different trust zones
until the operator explicitly chooses otherwise.
Required Inventory
Collect this before giving implementation steps:
| Area | Questions | |
|---|---|---|
| Internet edge | What is the modem or ONT? Is the ISP router bridged or still routing? | |
| Gateway | What routes, firewalls, handles DHCP, and terminates VPNs? | |
| Switching | Which switch ports are uplinks, access ports, trunks, or unmanaged? | |
| Wi-Fi | Which SSIDs map to which networks, and are APs wired or mesh? | |
| Addressing | What subnets exist today, and which ranges conflict with VPN sites? | |
| DNS/DHCP | Which service currently hands out leases and resolver addresses? | |
| Management | How will the operator reach the gateway, switch, and AP after changes? | |
| Recovery | What can be reverted locally if DNS, DHCP, VLANs, or VPN routes break? |
VLAN And Trust-Zone Plan
Start with intent rather than vendor syntax.
| Zone | Typical contents | Default policy | |
|---|---|---|---|
| Trusted | Laptops, phones, admin workstations | Can reach shared services and management only when needed | |
| Servers | NAS, Home Assistant, lab hosts, DNS resolver | Accepts narrow inbound flows from trusted clients | |
| IoT | TVs, smart plugs, cameras, speakers | Internet access plus explicit exceptions only | |
| Guest | Visitor devices | Internet-only, no LAN reachability | |
| Management | Gateway, switches, APs, controllers | Reachable only from trusted admin devices | |
| VPN | Remote clients | Same or narrower access than trusted clients |
Before recommending VLAN IDs or subnets, confirm:
- The gateway supports inter-VLAN routing and firewall rules.
- The switch supports the required tagged and untagged port behavior.
- The APs can map SSIDs to VLANs.
- The operator knows which port they are connected through during the change.
- The management network remains reachable after trunk and SSID changes.
DNS Filtering Readiness
Pi-hole or another local resolver should be introduced as a dependency, not as a single point of failure.
- Give the resolver a reserved address before using it in DHCP options.
- Confirm it can resolve public DNS and local
home.arpanames. - Keep the gateway or a second resolver available as a temporary fallback.
- Test one client or one VLAN before changing every DHCP scope.
- Document which networks may bypass filtering and why.
- Check that blocking rules do not break captive portals, work VPNs, firmware
updates, or medical/security devices.
Useful validation evidence:
Remote Access Readiness
For WireGuard-style access, decide what the VPN is allowed to reach before generating keys or opening ports.
| Mode | Use when | Risk notes | |
|---|---|---|---|
| Split tunnel to one subnet | Remote admin for NAS or lab hosts | Keep route list narrow | |
| Split tunnel to trusted services | Access selected apps by IP or DNS | Requires precise firewall rules | |
| Full tunnel | Untrusted networks or travel | More bandwidth and DNS responsibility | |
| Overlay VPN | Simpler remote access with identity controls | Still needs ACL review |
Do not recommend port forwarding until the operator confirms:
- The VPN endpoint is patched and actively maintained.
- The forwarded port goes only to the VPN service, not an admin UI.
- Dynamic DNS, public IP behavior, and ISP CGNAT status are understood.
- Peer keys can be revoked without rebuilding the whole network.
- Logs or connection status can verify who connected and when.
Change Sequence
Prefer small, reversible changes:
- Snapshot the current topology, IP plan, DHCP settings, DNS settings, and
firewall rules.
- Reserve infrastructure addresses for gateway, DNS, controller, APs, NAS, and
VPN endpoint.
- Create the new zone or VLAN without moving critical devices.
- Move one test client and validate DHCP, DNS, routing, internet, and block
behavior.
- Add narrow firewall exceptions for required flows.
- Move one low-risk device group.
- Add VPN access with the narrowest route and firewall policy that satisfies
the use case.
- Document final state, known exceptions, and rollback commands or UI steps.
Review Checklist
- Each network has a reason to exist and a clear trust boundary.
- No management interface is reachable from guest, IoT, or the public internet.
- DNS failure does not take down the operator's ability to recover locally.
- DHCP scope changes were tested on one client before broad rollout.
- VPN clients receive only the routes and DNS settings they need.
- Firewall rules are default-deny between zones, with named exceptions.
- The operator can still reach gateway, switch, AP, DNS, and VPN admin surfaces.
- Rollback is documented in the same vocabulary as the chosen platform UI or
CLI.
Anti-Patterns
- Segmenting networks before knowing which switch ports and SSIDs carry which
VLANs.
- Moving the admin workstation off the only reachable management network.
- Pointing all DHCP scopes at a Pi-hole before testing fallback DNS.
- Publishing NAS, DNS, router, or hypervisor management directly to the
internet.
- Treating VPN access as equivalent to full trusted-LAN access.
- Adding allow-all firewall rules temporarily and forgetting to remove them.
- Copying commands from another vendor or firmware version without checking the
exact platform syntax.
See Also
- Skill:
homelab-network-setup - Skill:
network-config-validation - Skill:
network-interface-health
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/homelab-network-readiness/SKILL.md
Popularity
- Repository stars
- 226,388
- Repository forks
- 34,627
- 7-day trend score
- 62
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 19 May 2026, 6 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/affaan-m/ecc/homelab-network-readiness)