All skills
network-protocol-gateway-usage
FoundationJIT onlyanalysis-agent/task-agent/review-agent: use when HTTP/TLS/DNS, proxies, ingress, headers, timeout chains, WebSocket, or gateways change; skip without network-edge impact.
- Group
- Reliability & operations
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- Nginx Envoy HAProxy Cloudflare Fastly CloudFront ALB NLB
- ingress API gateway service mesh WAF CDN reverse proxy load balancer
- TLS DNS SNI ALPN
- HTTP proxy header X-Forwarded-For Forwarded Host CORS
- WebSocket SSE gRPC timeout-chain
- 502 503 504 retry-amplification upstream-status edge origin trace context
- path-rewrite cache-key TTL invalidation purge stale-behavior per-user data health check origin shielding
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local network protocol gateway usage decision is required
Required inputs
What must be supplied before this skill can decide anything
- current task contract
- selected primary Professional Skill
- task-local trigger evidence
Output contract
What this skill owes the next role
- Network Gateway Record: map surfaces, hops, protocol, timeouts, retries, trusted headers, security, and observability; include decisions, validation commands, and residual risk
Escalation signals
When this skill must hand the decision back
- Gateway and protocol changes can mask upstream failures amplify retries trust spoofed headers break TLS or streaming behavior and produce 5xx symptoms without hop-chain evidence
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | timeout retry header TLS cache or streaming mechanisms remain undecided | current hop contracts and provider policy select one mechanism | TaskReviewAnalysis |
| checklist.mddecision-checklist | gateway changes affect hop trust deadlines retries TLS or protocol limits | no network hop or gateway behavior changes | TaskReviewAnalysis |
| evidence-patterns.mdevidence-pattern | routing timeout TLS or failing-hop claims need representative proof | fresh config probes and correlated telemetry prove each claim | TaskReviewAnalysis |