Individual skill

go-http-server-applications

Design, build, test, and review production Go HTTP servers covering inbound adapters, modern ServeMux routing, middleware, strict bounded request decoding, response commitment, transparent ResponseWriter wrapping, server timeouts, health semantics, graceful shutdown, shared-state safety, and httptest verification. Use when implementing an HTTP service, API handler, middleware stack, server lifecycle, health endpoint, or inbound JSON boundary in Go.

plugins/LVTD-LLC/skills/skills/go-http-server-applications/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
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,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Go HTTP Server Applications

Keep handlers thin, bound untrusted input, configure the server explicitly, and
make startup and shutdown part of the tested application contract.

## Core Workflow

1. Separate domain behavior from the inbound HTTP adapter.
2. Define routes, methods, media types, limits, and error mappings.
3. Build an explicit mux and ordered middleware stack.
4. Decode requests strictly and within endpoint-specific byte/time budgets.
5. Encode complete responses before committing headers where practical.
6. Configure listener, server timeouts, header limits, and health semantics.
7. Serve under a lifecycle that observes errors and drains with a deadline.