Prepare reproducible Go CLI artifacts across operating systems and architectures with toolchain-derived target matrices, capability profiles, portable config and cache discovery, CGO decisions, version metadata, artifact handoff, smoke tests, archives, checksums, containers, and versioned source installation.
NewMaintained
Automatic
◆Coding pack
Last verified 8/16/2026
What it changes
Passed 17 of 22 test cases with the skill, and 17 of 22 without it.
Without skill77%
With skill77%
Checks it passed that the model alone missed
The response states that release binaries should be built exactly once by a protected release job.
1 fixed16 passed either way4 still failing1 broke
Pass-rate lift
0 pp
Tokens
+9%
Agent turns
0%
Response time
-22%
Model gemini-3.6-flashMeasured 8/16/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
In a multi-stage distribution pipeline, how many times should final binaries be compiled when publishing across multiple distribution channels like GitHub Releases, DockerHub, and package managers?
What was checked, without and with the skill
Checked
Without skill
With skill
The response states that release binaries should be built exactly once by a protected release job.
Missed
Passed
case-17 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md57 linessingle file
Go CLI Distribution
Treat compilation as the start of release verification, not the finish. Declare
the matrix, record every build input, and execute the final artifacts.
Core Workflow
Derive supported GOOS/GOARCH targets from the pinned toolchain and dependencies.
Verify platform files and modern //go:build capability constraints.
Apply build, verification, container, and install rules
references/distribution/rules.md
Implement constraints or build commands
references/distribution/examples.md
Use cross-build, CGO, metadata, or container patterns
references/distribution/patterns.md
Review release readiness
references/distribution/checklist.md
Understand portability and artifact tradeoffs
references/distribution/knowledge.md
Guardrails
Use //go:build; do not introduce legacy-only // +build constraints.
Do not assume CGO_ENABLED=0 proves a self-contained artifact.
Cross-compilation alone does not establish runtime support.
Generate checksums only after final packaging and verify them after upload.
Use platform config and cache directory APIs; do not assume Unix home layouts.
Treat build tags as capability selection, never authentication or authorization.
Define and snapshot-test the artifact contract before release. The protected
tagged release job builds final bytes once; downstream channels must not rebuild them.
Recommend go install module/cmd/tool@version, not go get, for executable installation.