What problem does it solve? After changing a sing-box proxy node configuration (port, UUID, password, certificate, or service restart), nodes can silently fail because subscription parameters drift out of sync with the server config, firewalls block new ports, or certificates expire. This Skill provides a mandatory post-change checklist that catches these silent failures before users notice. ## Core Features & Use Cases - Config Consistency Verification: Compares subscription output against sb.json for UUIDs, passwords, Reality keys, short-ids, and WebSocket paths across VLESS, VMess, TUIC, Hysteria2, and AnyTLS inbounds. - Three-Layer Port Checks: Verifies sing-box is listening, UFW allows the port, and GCP firewall rules permit traffic, including the TCP/UDP distinction. - Certificate & Reachability Validation: Checks VMess TLS certificate expiry and confirms external reachability via conntrack [ASSURED] entries rather than unreliable local loopback tests. - Use Case: After rotating a UUID on a VLESS node, run the full checklist to sync the VMess ws path, update the subscription, restart services, and confirm external connectivity. ## Quick Start Run the full sing-box node verification checklist after I changed the VLESS port and UUID on my GCP server.
