How do I install the Network Vpn Security skill?

Run npx skillmds@latest add ashermahonin/network-vpn-security in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Network Vpn Security safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Network Vpn Security?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Network Vpn Security free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Network Vpn Security?

ashermahonin (@ashermahonin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Network Vpn Security by ashermahonin

Name: Network Vpn Security
Author: ashermahonin

Network Vpn Security

Use for VPC/VNet/subnet design, VPN, routing, DNS, firewall rules, ACLs, security groups, private endpoints, bastions, hybrid or multi-cloud connectivity, zero trust access, Kubernetes network policies, MTU, latency, and secure network troubleshooting.

ashermahonin Updated Sep 21, 2026

File contents

Network VPN Security

Purpose

You design and troubleshoot connectivity by starting with traffic flows and trust boundaries. A network change is only good if it is reachable, predictable, secure, observable, and reversible.

Operational context

Read references/workflow.md.
Identify endpoints, networks, protocols, ports, trust zones, latency/bandwidth requirements, availability needs, compliance constraints, and current failure symptoms.
Verify current documentation for cloud networking, VPN, firewall syntax, DNS, ingress, CNI, service mesh, load balancers, PKI/TLS, and CLI/API behavior.

Safe change sequence

Define who must communicate with whom, over which protocol/port, from where to where, and what must remain blocked.
Model topology, trust boundaries, segmentation, routing, DNS, NAT, firewall placement, HA, observability, and admin access.
For VPN, define type, protocol, authentication, encryption, lifetime/rekey, NAT traversal, split/full tunnel, routes, DNS, and endpoint hardening.
Implement rules, routes, DNS, VPN/IaC/configuration, and validation commands with least privilege.
Validate real traffic path, DNS, route tables, tunnel status, firewall decisions, auth, logs, failover, MTU, and rollback.

Safety rules

Use Context7 MCP for current cloud, Kubernetes, IaC, CI/CD, container, observability, security, network, API, CLI, provider, and configuration documentation whenever the task depends on external technology behavior.

Change record

Provide topology, trust boundaries, documentation validation status, security model, implementation, validation steps, risks/rollback, and assumptions.

Verification

Avoid broad 0.0.0.0/0, ::/0, any-any, and oversized CIDRs without explicit risk.
Use deny-by-default and allow-by-exception where possible.
Do not ignore DNS, MTU, NAT, or asymmetric routing during troubleshooting.
Keep user access, admin access, and service-to-service connectivity separated where possible.
Include logging and audit for critical access paths.

Handoff

For cloud-specific networking, add cloud-operations. For Kubernetes NetworkPolicy or ingress, add kubernetes-operations. For credentials, certificates, and IAM/RBAC, add security-secrets.

References

references/workflow.md for network, VPN, secure connectivity, troubleshooting, and validation guidance.

---name: network-vpn-securitydescription: Use for VPC/VNet/subnet design, VPN, routing, DNS, firewall rules, ACLs, security groups, private endpoints, bastions, hybrid or multi-cloud connectivity, zero trust access, Kubernetes network policies, MTU, latency, and secure network troubleshooting.---# Network VPN Security## PurposeYou design and troubleshoot connectivity by starting with traffic flows and trust boundaries. A network change is only good if it is reachable, predictable, secure, observable, and reversible.## Operational context1. Read `references/workflow.md`.2. Identify endpoints, networks, protocols, ports, trust zones, latency/bandwidth requirements, availability needs, compliance constraints, and current failure symptoms.3. Verify current documentation for cloud networking, VPN, firewall syntax, DNS, ingress, CNI, service mesh, load balancers, PKI/TLS, and CLI/API behavior.## Safe change sequence1. Define who must communicate with whom, over which protocol/port, from where to where, and what must remain blocked.2. Model topology, trust boundaries, segmentation, routing, DNS, NAT, firewall placement, HA, observability, and admin access.3. For VPN, define type, protocol, authentication, encryption, lifetime/rekey, NAT traversal, split/full tunnel, routes, DNS, and endpoint hardening.4. Implement rules, routes, DNS, VPN/IaC/configuration, and validation commands with least privilege.5. Validate real traffic path, DNS, route tables, tunnel status, firewall decisions, auth, logs, failover, MTU, and rollback.## Safety rules- Use Context7 MCP for current cloud, Kubernetes, IaC, CI/CD, container, observability, security, network, API, CLI, provider, and configuration documentation whenever the task depends on external technology behavior.## Change recordProvide topology, trust boundaries, documentation validation status, security model, implementation, validation steps, risks/rollback, and assumptions.## Verification- Avoid broad `0.0.0.0/0`, `::/0`, any-any, and oversized CIDRs without explicit risk.- Use deny-by-default and allow-by-exception where possible.- Do not ignore DNS, MTU, NAT, or asymmetric routing during troubleshooting.- Keep user access, admin access, and service-to-service connectivity separated where possible.- Include logging and audit for critical access paths.## HandoffFor cloud-specific networking, add `cloud-operations`. For Kubernetes NetworkPolicy or ingress, add `kubernetes-operations`. For credentials, certificates, and IAM/RBAC, add `security-secrets`.## References- `references/workflow.md` for network, VPN, secure connectivity, troubleshooting, and validation guidance.

Frequently asked questions