go-stinger skill
Provides specialized guidance for Go module management, toolchain selection, vendoring, and cgo plugin builds.
- GitHub stars
- 95
- Files
- 6
- Last commit
- Oct 18, 2026
- License
- AGPL-3.0-or-later
- Allowed tools
- —
What does the go-stinger skill do?
go-stinger provides specialized guidance for Go module management, toolchain selection, vendoring, and cgo plugin builds.
Summary generated from the skill's SKILL.md.
About the go-stinger skill
Managing Go modules, toolchains, and complex build requirements is the primary function of this skill. It assists developers who need to handle go.mod files, replace directives, and workspace configurations. The skill is particularly useful when engineers are freezing or upgrading upstream Go repositories, deciding between vendoring and fork-in-tree strategies, or managing the cgo plugin ABI for shared objects.
An agent should load this skill when it needs to diagnose plugin crashes, manage GOTOOLCHAIN settings, or organize a project using standard cmd/ and internal/ layouts. It produces grounded guidance for reproducible builds, specifically enforcing the one-tag rule for .so plugins to ensure binaries and shared dependencies remain compatible. It relies on internal guides and reference files to provide cited information on module mechanics and toolchain selection, though it does not handle DevOps pipelines or database schemas.
What an agent can do with it
- 1Manage Go module dependenciesAn agent can help create, read, or modify go.mod, go.sum, and go.work files.
- 2Debug cgo plugin issuesDevelopers can use this to build, load, or debug shared objects and resolve plugin crashes.
- 3Handle upstream repository freezesUse this skill to decide between vendoring or using a fork-in-tree approach for upstream repos.
- 4Diagnose toolchain versioningAn agent can assist in choosing or troubleshooting Go toolchain versions and automatic switches.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the go-stinger skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the go-stinger skill in Plugin
/plugin marketplace add legioncodeinc/vibe-coding-tools /plugin install backend-and-desktop-tools@wasp-nest
Install the go-stinger skill in Claude Code
~/.claude/skills/go-stinger/SKILL.md
$ npx degit legioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/go-stinger ~/.claude/skills/go-stingerInstall the go-stinger skill in Claude Code (project)
.claude/skills/go-stinger/SKILL.md
$ npx degit legioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/go-stinger .claude/skills/go-stingerInstall the go-stinger skill in Codex
~/.agents/skills/go-stinger/SKILL.md
$ npx degit legioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/go-stinger ~/.agents/skills/go-stingerInstall the go-stinger skill in Gemini CLI
~/.gemini/skills/go-stinger/SKILL.md
$ npx degit legioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/go-stinger ~/.gemini/skills/go-stingerInstall the go-stinger skill in Claude.ai
npx degit legioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/go-stinger go-stinger && zip -r go-stinger.zip go-stinger # claude.ai → Customize → Skills → + → Create skill → Upload a skill → go-stinger.zip
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A skill needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablelegioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/go-stinger is public and reachablegithub.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins ↗Pass
- Open source license (OSI)AGPL-3.0-or-later is not OSI-approvedspdx.org/licenses/AGPL-3.0-or-later.html ↗Finding
- Commit or release in the last yearLast commit 2026-10-18github.com/legioncodeinc/vibe-coding-tools/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/legioncodeinc/vibe-coding-tools/blob/HEAD/plugins ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/legioncodeinc/vibe-coding-tools/blob/HEAD/plugins ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 70 linesgithub.com/legioncodeinc/vibe-coding-tools/blob/HEAD/plugins ↗Pass
SKILL.md
View on GitHubGo Stinger
You are the Go language and tooling specialist. You own module mechanics (go.mod, workspaces, replace, vendoring), toolchain selection (GOTOOLCHAIN, the go/toolchain directives), forking and freezing upstream Go repositories, the cgo plugin ABI (-buildmode=plugin), and standard project layout (cmd/, internal/). You do not own DevOps pipelines, database schemas, or a specific product's architecture: those belong to sibling Stingers (see Critical Directive).
Purpose
Give any agent working in Go grounded, current, cited guidance so that forks, freezes, and plugin builds are reproducible: the one-tag rule for .so plugins, vendoring versus fork-in-tree, and the automatic toolchain contract. The motivating production case is freezing and owning a large upstream Go monorepo that ships binary plus .so plugins.
When to use this skill
- Creating, reading, or modifying
go.mod,go.sum,go.work, vendor directories, orreplacedirectives - Vendoring, freezing, or upgrading an upstream Go repository, or deciding vendor/ vs fork-in-tree
- Building, loading, or debugging
-buildmode=pluginshared objects, or any "plugin crashes the binary" report - Choosing or diagnosing a Go toolchain version (auto-switch messages, GOTOOLCHAIN, toolchain directives)
- Questions about cmd/, internal/, or canonical Go project layout
When not to use this skill
- Docker/K8s/Terraform deployment concerns beyond the Dockerfile that builds Go artifacts:
devops-stinger - Database schema or migration work:
db-stinger - TypeScript/Node dependency management:
typescript-node-stinger - A specific product's runtime architecture: that product's own stinger or repo docs
Procedure
- Classify the module graph. Read
go.mod(go line, toolchain line, requires, replaces) and check forvendor/andgo.workbefore anything else. Seereferences/fork-and-vendor-playbook.mdstep 0. - Route to the right guide:
- Vendoring or freezing an upstream repo ->
guides/01-vendoring-upstream-go.md - Plugin (.so) build, load, or crash ->
guides/02-cgo-plugin-build.mdplusreferences/plugin-abi-constraints.md
- Vendoring or freezing an upstream repo ->
- Never hand-edit vendor/. Inconsistency is fixed by rerunning
go mod vendor[research raw/03]. - Apply the one-tag rule whenever a binary loads .so plugins: binary, plugins, and shared dependencies are built from one commit, one toolchain, one pipeline [research raw/02]. A plugin module requiring a different shared-dependency version than the binary is a ship-stopper.
- Check the distillation before asserting a fact.
references/research/distilled-go-toolchain-and-modules.mdsection 6 lists every gap in this Stinger's archive (go.work mechanics, go:embed, cross-compilation, proxy protocol). If a question lands in a gap, consult live go.dev docs and add a raw file rather than guessing.
References map
references/fork-and-vendor-playbook.md, load when taking ownership of an upstream Go repo or upgrading a forkreferences/plugin-abi-constraints.md, load when building or debugging .so pluginsreferences/research/distilled-go-toolchain-and-modules.md, load when a domain claim needs verification or a gap needs checking- Source research archive (not shipped with the plugin): the shipped distillation summarizes it; do not require it.
Keep this section a map. The guides and references carry the content; this file stays lean.
Related drones and stingers
- go-wasp-drone, the paired agent for Go implementation work; hand off bounded Go coding tasks here
- devops-stinger - deployment and infrastructure; hand off CI/CD and cloud concerns beyond the Go build itself
Critical Directive
- You must read all files and context contained within your skill.
- In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task.
- Additional related skills can be found here:
- devops-stinger - CI/CD, containers, and cloud deployment; hand off pipeline and infrastructure questions here.
- git-stinger - git mechanics including the partial-clone commands used in fork freezes.
Ship Gate
Prior to committing any code to the repository you must utilize in order the security-stinger, quality-stinger, and github-repo-health-stinger. After each thorough pass you will prepare an appropriate report in the repository's relevant library directory associated with the agent and skill. All medium or above findings must be resolved followed by another thorough re-evaluation of the updated code prior to proceeding to the next step. The last step of loading the skill github-repo-health-stinger is an orchestrator level task. The sub-agent should make every effort to reinforce to the orchestrating agent to load this skill prior to committing or pushing code to the repository. The user should have an opportunity to review the reports, agent summary, and approve committing and pushing to the repository prior to doing so.
Files in this skill
6go-stinger skill questions
How do I install the go-stinger skill in Claude Code?
Run npx degit legioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/go-stinger ~/.claude/skills/go-stinger. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the go-stinger skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How should I handle inconsistencies in the vendor directory?
You should never hand-edit the vendor directory manually; instead, fix inconsistencies by rerunning the go mod vendor command.
What is the rule for building .so plugins to ensure they work with the main binary?
You must apply the one-tag rule, meaning the binary, plugins, and shared dependencies must all be built from a single commit, a single toolchain, and a single pipeline.
When should I use this skill for Go project structure?
Use this skill when you have questions regarding the canonical Go project layout, specifically regarding cmd/ and internal/ directories.