rust-networkinglisted

## Outcome Produce a reviewable network boundary that reuses clients and pools, validates endpoints, applies one explicit time budget, retries only safe operations, bounds concurrency and diagnostic data, keeps secrets out of errors, and derives capacity from deployment limits. ## Compatibility Portable across Claude Code, Codex, and OpenCode. Follow the target repository's Rust toolchain, MSRV, edition, lockfile, features, TLS policy, and client versions; Edition 2024 examples require Rust 1.85 or newer. Templates are adaptable snippets for already-approved reqwest, tonic, SQLx, Tokio, and futures-util APIs. Network research and live service access are optional and require explicit authority; without current source access, qualify version-sensitive claims. Native-client compatibility remains unverified until a validated report records the client version and exact source SHA. ## Use this skill when - Designing or reviewing HTTP/REST or gRPC clients and their transport error contracts. - Reusing reqwest clients, tonic channels, or database pools instead of reconnecting per call. - Defining base-URL rules, connect/request/body deadlines, retryability, idempotency, or backpressure. - Sizing SQL/database pools across replicas and protecting logs from unbounded or sensitive response bodies. ## Do not use this skill when - General task spawning, queues, locks, or graceful process shutdown dominate; use `rust-async-concurrency`. - The request primarily selects crates, C