[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APVGTG79QJSD5EG6QPJH2X":3,"skill-same:01M7APVGTG79QJSD5EG6QPJH2X":49},{"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":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7APVGTG79QJSD5EG6QPJH2X","homelab-network-readiness",null,"Readiness checklist for homelab VLAN segmentation, local DNS filtering, and WireGuard-style remote access before changing router, firewall, DHCP, or VPN configuration.","Cyrilthetecchieee\u002Fcyril-code-","Cyrilthetecchieee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219787998?v=4","01M7AF0MMMKRAA0H61XMJPV92H","Julian Cyril D ","01M7AF0MQ10AVG6QJQ1C2BC0F5",2,"MIT","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fhomelab-network-readiness\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: homelab-network-readiness\ndescription: Readiness checklist for homelab VLAN segmentation, local DNS filtering, and WireGuard-style remote access before changing router, firewall, DHCP, or VPN configuration.\nmetadata:\n  origin: community\n---\n\n# Homelab Network Readiness\n\nUse this skill before changing a home or small-lab network that mixes VLANs,\nPi-hole or another local DNS resolver, firewall rules, and remote VPN access.\n\nThis is a planning and review skill. Do not turn it into copy-paste router,\nfirewall, or VPN configuration unless the target platform, current topology,\nrollback path, console access, and maintenance window are all known.\n\n## When to Use\n\n- Preparing to split a flat network into trusted, IoT, guest, server, or\n  management VLANs.\n- Moving DHCP clients to Pi-hole, AdGuard Home, Unbound, or another local DNS\n  resolver.\n- Adding WireGuard, Tailscale, ZeroTier, OpenVPN, or router-native VPN access.\n- Reviewing whether a homelab change can lock the operator out of the gateway,\n  switch, access point, DNS server, or VPN server.\n- Turning an informal home-network idea into a staged migration plan with\n  validation evidence.\n\n## Safety Rules\n\n- Keep the first answer read-only: inventory, risks, staged plan, validation,\n  and rollback.\n- Do not expose gateway admin panels, DNS resolvers, SSH, NAS consoles, or VPN\n  management UIs directly to the public internet.\n- Do not provide firewall, NAT, VLAN, DHCP, or VPN commands without a confirmed\n  platform and a rollback procedure.\n- Require out-of-band or same-room console access before changing management\n  VLANs, trunk ports, firewall default policies, or DHCP\u002FDNS settings.\n- Keep a working path back to the internet before pointing the whole network at\n  a new DNS resolver or VPN route.\n- Treat IoT, guest, camera, and lab-server networks as different trust zones\n  until the operator explicitly chooses otherwise.\n\n## Required Inventory\n\nCollect this before giving implementation steps:\n\n| Area | Questions |\n| --- | --- |\n| Internet edge | What is the modem or ONT? Is the ISP router bridged or still routing? |\n| Gateway | What routes, firewalls, handles DHCP, and terminates VPNs? |\n| Switching | Which switch ports are uplinks, access ports, trunks, or unmanaged? |\n| Wi-Fi | Which SSIDs map to which networks, and are APs wired or mesh? |\n| Addressing | What subnets exist today, and which ranges conflict with VPN sites? |\n| DNS\u002FDHCP | Which service currently hands out leases and resolver addresses? |\n| Management | How will the operator reach the gateway, switch, and AP after changes? |\n| Recovery | What can be reverted locally if DNS, DHCP, VLANs, or VPN routes break? |\n\n## VLAN And Trust-Zone Plan\n\nStart with intent rather than vendor syntax.\n\n| Zone | Typical contents | Default policy |\n| --- | --- | --- |\n| Trusted | Laptops, phones, admin workstations | Can reach shared services and management only when needed |\n| Servers | NAS, Home Assistant, lab hosts, DNS resolver | Accepts narrow inbound flows from trusted clients |\n| IoT | TVs, smart plugs, cameras, speakers | Internet access plus explicit exceptions only |\n| Guest | Visitor devices | Internet-only, no LAN reachability |\n| Management | Gateway, switches, APs, controllers | Reachable only from trusted admin devices |\n| VPN | Remote clients | Same or narrower access than trusted clients |\n\nBefore recommending VLAN IDs or subnets, confirm:\n\n1. The gateway supports inter-VLAN routing and firewall rules.\n2. The switch supports the required tagged and untagged port behavior.\n3. The APs can map SSIDs to VLANs.\n4. The operator knows which port they are connected through during the change.\n5. The management network remains reachable after trunk and SSID changes.\n\n## DNS Filtering Readiness\n\nPi-hole or another local resolver should be introduced as a dependency, not as a\nsingle point of failure.\n\n1. Give the resolver a reserved address before using it in DHCP options.\n2. Confirm it can resolve public DNS and local `home.arpa` names.\n3. Keep the gateway or a second resolver available as a temporary fallback.\n4. Test one client or one VLAN before changing every DHCP scope.\n5. Document which networks may bypass filtering and why.\n6. Check that blocking rules do not break captive portals, work VPNs, firmware\n   updates, or medical\u002Fsecurity devices.\n\nUseful validation evidence:\n\n```text\nClient gets expected DHCP lease\nClient receives expected DNS resolver\nPublic DNS lookup succeeds\nLocal home.arpa lookup succeeds\nBlocked test domain is blocked only where intended\nGateway and DNS admin interfaces are not reachable from guest or IoT networks\n```\n\n## Remote Access Readiness\n\nFor WireGuard-style access, decide what the VPN is allowed to reach before\ngenerating keys or opening ports.\n\n| Mode | Use when | Risk notes |\n| --- | --- | --- |\n| Split tunnel to one subnet | Remote admin for NAS or lab hosts | Keep route list narrow |\n| Split tunnel to trusted services | Access selected apps by IP or DNS | Requires precise firewall rules |\n| Full tunnel | Untrusted networks or travel | More bandwidth and DNS responsibility |\n| Overlay VPN | Simpler remote access with identity controls | Still needs ACL review |\n\nDo not recommend port forwarding until the operator confirms:\n\n- The VPN endpoint is patched and actively maintained.\n- The forwarded port goes only to the VPN service, not an admin UI.\n- Dynamic DNS, public IP behavior, and ISP CGNAT status are understood.\n- Peer keys can be revoked without rebuilding the whole network.\n- Logs or connection status can verify who connected and when.\n\n## Change Sequence\n\nPrefer small, reversible changes:\n\n1. Snapshot the current topology, IP plan, DHCP settings, DNS settings, and\n   firewall rules.\n2. Reserve infrastructure addresses for gateway, DNS, controller, APs, NAS, and\n   VPN endpoint.\n3. Create the new zone or VLAN without moving critical devices.\n4. Move one test client and validate DHCP, DNS, routing, internet, and block\n   behavior.\n5. Add narrow firewall exceptions for required flows.\n6. Move one low-risk device group.\n7. Add VPN access with the narrowest route and firewall policy that satisfies\n   the use case.\n8. Document final state, known exceptions, and rollback commands or UI steps.\n\n## Review Checklist\n\n- Each network has a reason to exist and a clear trust boundary.\n- No management interface is reachable from guest, IoT, or the public internet.\n- DNS failure does not take down the operator's ability to recover locally.\n- DHCP scope changes were tested on one client before broad rollout.\n- VPN clients receive only the routes and DNS settings they need.\n- Firewall rules are default-deny between zones, with named exceptions.\n- The operator can still reach gateway, switch, AP, DNS, and VPN admin surfaces.\n- Rollback is documented in the same vocabulary as the chosen platform UI or\n  CLI.\n\n## Anti-Patterns\n\n- Segmenting networks before knowing which switch ports and SSIDs carry which\n  VLANs.\n- Moving the admin workstation off the only reachable management network.\n- Pointing all DHCP scopes at a Pi-hole before testing fallback DNS.\n- Publishing NAS, DNS, router, or hypervisor management directly to the\n  internet.\n- Treating VPN access as equivalent to full trusted-LAN access.\n- Adding allow-all firewall rules temporarily and forgetting to remove them.\n- Copying commands from another vendor or firmware version without checking the\n  exact platform syntax.\n\n## See Also\n\n- Skill: `homelab-network-setup`\n- Skill: `network-config-validation`\n- Skill: `network-interface-health`\n","# Homelab Network Readiness\n\nUse this skill before changing a home or small-lab network that mixes VLANs,\nPi-hole or another local DNS resolver, firewall rules, and remote VPN access.\n\nThis is a planning and review skill. Do not turn it into copy-paste router,\nfirewall, or VPN configuration unless the target platform, current topology,\nrollback path, console access, and maintenance window are all known.\n\n## When to Use\n\n- Preparing to split a flat network into trusted, IoT, guest, server, or\n  management VLANs.\n- Moving DHCP clients to Pi-hole, AdGuard Home, Unbound, or another local DNS\n  resolver.\n- Adding WireGuard, Tailscale, ZeroTier, OpenVPN, or router-native VPN access.\n- Reviewing whether a homelab change can lock the operator out of the gateway,\n  switch, access point, DNS server, or VPN server.\n- Turning an informal home-network idea into a staged migration plan with\n  validation evidence.\n\n## Safety Rules\n\n- Keep the first answer read-only: inventory, risks, staged plan, validation,\n  and rollback.\n- Do not expose gateway admin panels, DNS resolvers, SSH, NAS consoles, or VPN\n  management UIs directly to the public internet.\n- Do not provide firewall, NAT, VLAN, DHCP, or VPN commands without a confirmed\n  platform and a rollback procedure.\n- Require out-of-band or same-room console access before changing management\n  VLANs, trunk ports, firewall default policies, or DHCP\u002FDNS settings.\n- Keep a working path back to the internet before pointing the whole network at\n  a new DNS resolver or VPN route.\n- Treat IoT, guest, camera, and lab-server networks as different trust zones\n  until the operator explicitly chooses otherwise.\n\n## Required Inventory\n\nCollect this before giving implementation steps:\n\n| Area | Questions |\n| --- | --- |\n| Internet edge | What is the modem or ONT? Is the ISP router bridged or still routing? |\n| Gateway | What routes, firewalls, handles DHCP, and terminates VPNs? |\n| Switching | Which switch ports are uplinks, access ports, trunks, or unmanaged? |\n| Wi-Fi | Which SSIDs map to which networks, and are APs wired or mesh? |\n| Addressing | What subnets exist today, and which ranges conflict with VPN sites? |\n| DNS\u002FDHCP | Which service currently hands out leases and resolver addresses? |\n| Management | How will the operator reach the gateway, switch, and AP after changes? |\n| Recovery | What can be reverted locally if DNS, DHCP, VLANs, or VPN routes break? |\n\n## VLAN And Trust-Zone Plan\n\nStart with intent rather than vendor syntax.\n\n| Zone | Typical contents | Default policy |\n| --- | --- | --- |\n| Trusted | Laptops, phones, admin workstations | Can reach shared services and management only when needed |\n| Servers | NAS, Home Assistant, lab hosts, DNS resolver | Accepts narrow inbound flows from trusted clients |\n| IoT | TVs, smart plugs, cameras, speakers | Internet access plus explicit exceptions only |\n| Guest | Visitor devices | Internet-only, no LAN reachability |\n| Management | Gateway, switches, APs, controllers | Reachable only from trusted admin devices |\n| VPN | Remote clients | Same or narrower access than trusted clients |\n\nBefore recommending VLAN IDs or subnets, confirm:\n\n1. The gateway supports inter-VLAN routing and firewall rules.\n2. The switch supports the required tagged and untagged port behavior.\n3. The APs can map SSIDs to VLANs.\n4. The operator knows which port they are connected through during the change.\n5. The management network remains reachable after trunk and SSID changes.\n\n## DNS Filtering Readiness\n\nPi-hole or another local resolver should be introduced as a dependency, not as a\nsingle point of failure.\n\n1. Give the resolver a reserved address before using it in DHCP options.\n2. Confirm it can resolve public DNS and local `home.arpa` names.\n3. Keep the gateway or a second resolver available as a temporary fallback.\n4. Test one client or one VLAN before changing every DHCP scope.\n5. Document which networks may bypass filtering and why.\n6. Check that blocking rules do not break captive portals, work VPNs, firmware\n   updates, or medical\u002Fsecurity devices.\n\nUseful validation evidence:\n\n```text\nClient gets expected DHCP lease\nClient receives expected DNS resolver\nPublic DNS lookup succeeds\nLocal home.arpa lookup succeeds\nBlocked test domain is blocked only where intended\nGateway and DNS admin interfaces are not reachable from guest or IoT networks\n```\n\n## Remote Access Readiness\n\nFor WireGuard-style access, decide what the VPN is allowed to reach before\ngenerating keys or opening ports.\n\n| Mode | Use when | Risk notes |\n| --- | --- | --- |\n| Split tunnel to one subnet | Remote admin for NAS or lab hosts | Keep route list narrow |\n| Split tunnel to trusted services | Access selected apps by IP or DNS | Requires precise firewall rules |\n| Full tunnel | Untrusted networks or travel | More bandwidth and DNS responsibility |\n| Overlay VPN | Simpler remote access with identity controls | Still needs ACL review |\n\nDo not recommend port forwarding until the operator confirms:\n\n- The VPN endpoint is patched and actively maintained.\n- The forwarded port goes only to the VPN service, not an admin UI.\n- Dynamic DNS, public IP behavior, and ISP CGNAT status are understood.\n- Peer keys can be revoked without rebuilding the whole network.\n- Logs or connection status can verify who connected and when.\n\n## Change Sequence\n\nPrefer small, reversible changes:\n\n1. Snapshot the current topology, IP plan, DHCP settings, DNS settings, and\n   firewall rules.\n2. Reserve infrastructure addresses for gateway, DNS, controller, APs, NAS, and\n   VPN endpoint.\n3. Create the new zone or VLAN without moving critical devices.\n4. Move one test client and validate DHCP, DNS, routing, internet, and block\n   behavior.\n5. Add narrow firewall exceptions for required flows.\n6. Move one low-risk device group.\n7. Add VPN access with the narrowest route and firewall policy that satisfies\n   the use case.\n8. Document final state, known exceptions, and rollback commands or UI steps.\n\n## Review Checklist\n\n- Each network has a reason to exist and a clear trust boundary.\n- No management interface is reachable from guest, IoT, or the public internet.\n- DNS failure does not take down the operator's ability to recover locally.\n- DHCP scope changes were tested on one client before broad rollout.\n- VPN clients receive only the routes and DNS settings they need.\n- Firewall rules are default-deny between zones, with named exceptions.\n- The operator can still reach gateway, switch, AP, DNS, and VPN admin surfaces.\n- Rollback is documented in the same vocabulary as the chosen platform UI or\n  CLI.\n\n## Anti-Patterns\n\n- Segmenting networks before knowing which switch ports and SSIDs carry which\n  VLANs.\n- Moving the admin workstation off the only reachable management network.\n- Pointing all DHCP scopes at a Pi-hole before testing fallback DNS.\n- Publishing NAS, DNS, router, or hypervisor management directly to the\n  internet.\n- Treating VPN access as equivalent to full trusted-LAN access.\n- Adding allow-all firewall rules temporarily and forgetting to remove them.\n- Copying commands from another vendor or firmware version without checking the\n  exact platform syntax.\n\n## See Also\n\n- Skill: `homelab-network-setup`\n- Skill: `network-config-validation`\n- Skill: `network-interface-health`\n",{"name":5,"metadata":24,"description":7},{"origin":25},"community","main","57e7aa6b6e03bce1a7d7862ba9c2ec312f7f19b5","src\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fhomelab-network-readiness",0,"https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee","https:\u002F\u002Fwithcyril.me\u002F","Hi, I’m Julian Cyril D, a Computer Science and Business Systems student at PSNACET.\r\nI’m passionate about full-stack development, UI\u002FUX design, and building sma","2026-11-04 23:28:50",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Cyrilthetecchieee\u002Fcyril-code- --skill homelab-network-readiness",{"tool":41,"command":42},"bunx","bunx skills add Cyrilthetecchieee\u002Fcyril-code- --skill homelab-network-readiness",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Cyrilthetecchieee\u002Fcyril-code- --skill homelab-network-readiness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fhomelab-network-readiness\u002FSKILL.md",true,[],[50,59,66,74,81,88],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":55,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7AQV6CYX8RMC78420V9WZ62","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7AQV2895N3S1MEX6K76G6G2","youtube-downloader","Download YouTube videos with customizable quality and format options. Use this skill when the user asks to download, save, or grab YouTube videos. Supports various quality settings (best, 1080p, 720p, 480p, 360p), multiple formats (mp4, webm, mkv), and audio-only downloads as MP3.","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fvideo-downloader\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7AQTRNX62DNKVZ5GXEHRBKB","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftheme-factory\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7AQTNNVHAAN9H6DA8T6ZVE0","template-skill","Replace with description of the skill and when Claude should use it.","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftemplate-skill\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7AQTJ3MQ6AKX152MEX2MYCC","tailored-resume-generator","Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftailored-resume-generator\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7AQTD7D5MYET2YWG7HG9WM3","slack-gif-creator","Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like \"make me a GIF for Slack of X doing Y\".","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fslack-gif-creator\u002FSKILL.md",[],[]]