About this skill

Problem

When cloud networks, Kubernetes, load balancing, DNS, TLS, zero trust, and troubleshooting appear in the same architecture, issues can become fragmented across tooling. This skill treats them as one network-engineering workflow: define goals, constraints, and inputs first, then validate connectivity, security, performance, monitoring, and recovery paths end to end.

How It Works

It focuses on modern cloud networking and operations, covering AWS, Azure, GCP, load balancers, DNS and service discovery, SSL/TLS, PKI, firewalls, VPNs, service meshes, container networks, CDN, HTTP/2, HTTP/3, and eBPF.
Responses follow a practical sequence: requirements analysis, architecture design, connectivity implementation, security controls, monitoring, tuning, topology documentation, disaster recovery, and testing. It also provides actionable checks, such as using tcpdump, dig, openssl s_client, cloud flow logs, or service mesh metrics.

Boundaries

It is best for network design review, implementation, incident analysis, and automation planning, but it does not replace change approval, compliance audits, or low-level device debugging. If the task is primarily application logic, database design, or another non-network area, choose a different skill.