Individual skill
go-http-client-resilience
Design, implement, test, and review resilient Go HTTP client boundaries with context propagation, layered timeouts, transport reuse, request construction, authentication, status classification, bounded bodies, retry safety, backoff, rate limits, pagination, observability, and deterministic fakes. Use when a Go CLI or service calls remote APIs or when HTTP behavior is slow, flaky, unsafe, or hard to test.
plugins/LVTD-LLC/skills/skills/go-http-client-resilience/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,539
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- go,golang,http,client,resilience,retries,api Declared skill tag
- design Derived category
- security Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,854 bytesagents/openai.yamlasset · 235 bytesguidelines.mddoc · 1,566 bytesreferences/http-client-resilience/examples.mddoc · 2,262 bytesreferences/http-client-resilience/knowledge.mddoc · 2,596 bytesreferences/http-client-resilience/rules.mddoc · 2,474 bytesworkflows/build-http-client.mddoc · 1,988 bytes
Read excerpt
# Go HTTP Client Resilience
Treat HTTP as a failure-prone boundary with a finite time and resource budget.
Retry only when both the failure and the operation are safe.
## Core Workflow
1. Define operation semantics, total deadline, idempotency, and response limits.
2. Reuse a configured client and transport; propagate context into every request.
3. Construct URLs, headers, authentication, and bodies without secret leakage.
4. Classify transport, timeout, status, protocol, and decode failures.
5. Add bounded retries with jitter only for safe transient cases.
6. Drain or close bodies correctly and bound all reads.
7. Test with a function-backed transport and focused integration server.