# Design Secure, Reliable Networks

Complex cloud and container networks require coordinated decisions across connectivity, security, performance, and recovery. This skill provides structured architecture and troubleshooting guidance.

## Install

```bash
npx skillstore add sickn33/network-engineer
```

## Metadata

- Status: approved
- Slug: sickn33-network-engineer
- Skillstore revision: r2
- Version status: missing
- Tree hash: c6ce34b9966cd111235eabf4cb1b7805c769c20ea8952d2ba37698eac1ce7f69
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/network-engineer
- Ref: 81e05e636292629114b76cbb3922fbe57672fc02
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-network-engineer
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-network-engineer/manifest

## Capabilities

- Designs network architectures for AWS, Azure, GCP, hybrid, and multi-cloud environments.
- Recommends load balancing, DNS, service discovery, TLS, PKI, VPN, and zero-trust patterns.
- Guides troubleshooting across connectivity, DNS, certificates, latency, throughput, packet loss, and application protocols.
- Plans container networking and service mesh configurations for Kubernetes environments.
- Develops monitoring, redundancy, disaster recovery, capacity, and compliance strategies.
- Produces implementation steps, verification checks, rollback considerations, and architecture documentation.

## Use Cases

- Plan a Cloud Network: Create a secure VPC or virtual network design with routing, segmentation, shared services, and resilient connectivity.
- Resolve Service Connectivity: Build a layer-by-layer investigation for DNS, TLS, routing, policy, or service mesh failures.
- Review Network Controls: Assess segmentation, encryption, observability, failover, and compliance requirements before a production change.

## Prompt Templates

### Explain a Network Problem

```
Explain why [symptom] may occur in [environment]. List likely causes, required evidence, and safe verification steps.
```

### Create a Troubleshooting Plan

```
Create a layer-by-layer plan for [issue] in [environment]. Include checks for routing, DNS, TLS, policy, and observability.
```

### Design a Secure Architecture

```
Design network architecture for [workload] across [platforms]. Address segmentation, identity, encryption, ingress, egress, resilience, monitoring, and cost constraints.
```

### Evaluate a Production Migration

```
Review this migration plan: [plan]. Identify failure modes, security gaps, capacity risks, dependencies, test stages, rollback triggers, and acceptance criteria.
```

## Limitations

- The skill provides guidance and does not inspect, configure, or validate a live network independently.
- Recommendations require accurate topology, traffic, security, compliance, and platform details.
- Diagnostic actions require explicit authorization and environment-specific safety controls.
- The referenced implementation playbook is not included in this package.

## Best Practices

- Provide topology, platforms, traffic flows, constraints, recent changes, and measurable success criteria.
- Validate recommendations in a controlled environment before changing production routes, policies, DNS, or certificates.
- Use least privilege, documented authorization, staged testing, monitoring, and a verified rollback plan.

## Anti Patterns

- Do not run discovery or scanning tools against systems without explicit authorization and a defined scope.
- Do not apply generic configurations without checking platform limits, dependencies, security controls, and failure behavior.
- Do not make production network changes without observability, staged validation, communication, and rollback criteria.

## Security Audit

- Audited at: 2026-08-04T15:50:40.232\+00:00
- Summary: All four static findings are false positives caused by inline Markdown, networking terminology, and a contextual list of diagnostic tools. No malicious intent, command execution, prompt injection, or unauthorized scanning workflow was found.

## Stats

- Views: 112
- Downloads: 11
- Favorites: 1
- Popularity score: 0