Go Pedantry
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet.
Install Golang Tooling
$ npx skills add HoangNguyen0403/agent-skills-standard --skill golang-tooling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install HoangNguyen0403/agent-skills-standard golang-tooling --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/golang/golang-tooling .claude/skills/golang-tooling && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "golang-tooling" agent skill from https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/skills/golang/golang-tooling into .claude/skills/golang-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golang-tooling", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/skills/golang/golang-toolingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add HoangNguyen0403/agent-skills-standard --skill golang-tooling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install HoangNguyen0403/agent-skills-standard golang-tooling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/golang/golang-tooling .agents/skills/golang-tooling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "golang-tooling" agent skill from https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/skills/golang/golang-tooling into .agents/skills/golang-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golang-tooling", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add HoangNguyen0403/agent-skills-standard --skill golang-tooling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install HoangNguyen0403/agent-skills-standard golang-tooling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/golang/golang-tooling .cursor/skills/golang-tooling && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "golang-tooling" agent skill from https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/skills/golang/golang-tooling into .cursor/skills/golang-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golang-tooling", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/HoangNguyen0403/agent-skills-standard.git --path skills/golang/golang-tooling--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add HoangNguyen0403/agent-skills-standard --skill golang-tooling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install HoangNguyen0403/agent-skills-standard golang-tooling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/golang/golang-tooling .gemini/skills/golang-tooling && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "golang-tooling" agent skill from https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/skills/golang/golang-tooling into .gemini/skills/golang-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golang-tooling", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install HoangNguyen0403/agent-skills-standard golang-toolingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add HoangNguyen0403/agent-skills-standard --skill golang-tooling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/golang/golang-tooling .github/skills/golang-tooling && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "golang-tooling" agent skill from https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/skills/golang/golang-tooling into .github/skills/golang-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golang-tooling", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add HoangNguyen0403/agent-skills-standard --skill golang-tooling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install HoangNguyen0403/agent-skills-standard golang-tooling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/golang/golang-tooling .opencode/skills/golang-tooling && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "golang-tooling" agent skill from https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/skills/golang/golang-tooling into .opencode/skills/golang-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golang-tooling", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
golang-tooling- GitHub stars
- 572
- Token cost
- ~531 tokens
- SKILL.md length
- 184 words
- Files
- 3 (incl. references)
- Skills in repo
- 211
- Repo updated
- First seen
- Licence
- MIT
At a glance
Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet.
- Works in 4 steps: mcp__ide__getDiagnostics — gopls… → go vet ./... — catch printf mismatches,… → goimports -w . — organize imports and… → …
- Setting up Go tooling
- SKILL.md covers Priority: P1 (HIGH), Verification Workflow…, Tool Overview and golangci-lint Setup, plus 3 more sections
- Calls go
What it does
Golang Tooling is an agent skill from HoangNguyen0403/agent-skills-standard. Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Use when setting up Go tooling, running linters, or integrating gopls with Claude Code.
Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `evals/evals.json` and `references/golangci.md`).
It sits in Development, covering Linting and formatting. It works with Go. The repository describes itself as: A collection of Agent Skills Standard and Best Practice for Programming Languages, Frameworks that help our AI Agent follow best practies on frameworks and programming laguages. The licence is MIT.
When your agent uses it
- Setting up Go tooling
- Running linters
- Integrating gopls with Claude Code
Example prompts
- “/golang-tooling”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- mcp__ide__getDiagnostics — gopls real-time errors and type warnings (requires gopls-lsp plugin)
- go vet ./... — catch printf mismatches, unreachable code, shadowed variables
- goimports -w . — organize imports and format in one pass
- golangci-lint run ./... — run full linter suite (if .golangci.yml present)
What it can do on your machine
Read from SKILL.md and the folder at commit b529c2d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
go
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Golang Tooling loads about 531 tokens when it runs, and up to ~658 if it reads all its reference files. Until then it costs about 45 tokens; SKILL.md has 184 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from HoangNguyen0403/agent-skills-standard at commit b529c2d, republished under its MIT licence (© HoangNguyen0403). 184 words, ~531 tokens.
Download SKILL.mdSave it as
.claude/skills/golang-tooling/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- golang-tooling
- description
- Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Use when setting up Go tooling, running linters, or integrating gopls with Claude Code.
Golang Tooling Standards
Priority: P1 (HIGH)
Verification Workflow (Mandatory)
After writing or modifying Go code, run in order:
mcp__ide__getDiagnostics— gopls real-time errors and type warnings (requires gopls-lsp plugin)go vet ./...— catch printf mismatches, unreachable code, shadowed variablesgoimports -w .— organize imports and format in one passgolangci-lint run ./...— run full linter suite (if.golangci.ymlpresent)
Tool Overview
| Tool | Purpose | When to Use |
|---|---|---|
gopls | LSP: diagnostics, completion, hover | Always (IDE integration) |
go vet | Static analysis — correctness bugs | After every edit |
goimports | Import sorting + gofmt | Before commit |
golangci-lint | Aggregated linters (errcheck, staticcheck, etc.) | CI / pre-commit |
staticcheck | Advanced static analysis | Large codebases |
golangci-lint Setup
Configure via .golangci.yml at repo root. Recommended linters:
errcheck— enforce error handlingstaticcheck— bug detection beyond go vetgovet— shadow, compositesrevive— style enforcementgosec— security issues
See golangci.yml example.
gopls Integration
gopls powers mcp__ide__getDiagnostics. Install:
go install golang.org/x/tools/gopls@latestAnti-Patterns
- No
gofmtalone: Usegoimports— it formatting AND imports. - No manual import sorting: Let
goimportsmanage order. - No skipping go vet: Run it — catches real bugs
gofmtmisses. - No broad lint disable: Fix root cause instead of
//nolintcomments.
References
© HoangNguyen0403, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/golang/golang-tooling of HoangNguyen0403/agent-skills-standard.
- SKILL.md
- evals/evals.json
- references/golangci.md
Open the folder on GitHubat commit b529c2d
Compare with similar skills
Golang Tooling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Golang Tooling this skillHoangNguyen0403/agent-skills-standard | 572 | — | ~531 | Automated safety check: Pass | MIT | |
| Go Pedantrychromedp/chromedp | 13k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Golang Lintcontext-labs/whip | 1.1k | 2 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Golang Code Styleunxed/f4 | 244 | 3 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Validate Agent Workkryptamine/herdr-auto-title | 246 | — | ~605 | Automated safety check: Pass | MIT | |
| Golang Continuous Integrationsamber/cc-skills-golang | 3.4k | — | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Golang Lint
context-labs/whip
Linting best practices and golangci-lint configuration for Go — running linters, configuring .golangci.yml, nolint suppressions, selecting linters.
Golang Code Style
unxed/f4
Golang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt.
Validate Agent Work
kryptamine/herdr-auto-title
Final checklist before handing work back in the herdr-auto-title repo: review the diff, run make check, apply the comment and AGENTS.md rules, then report.
Golang Continuous Integration
samber/cc-skills-golang
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release…
Golang Continuous Integration
context-labs/whip
CI/CD with GitHub Actions for Golang — testing, linting, SAST, security scanning, coverage, Dependabot, Renovate, GoReleaser, release pipelines.
More from HoangNguyen0403/agent-skills-standard
All 211 skills in this repoSubagent-Driven Development
HoangNguyen0403/agent-skills-standard
Runs a multi-task implementation plan by sending each task to a fresh implementer subagent, reviewing it independently, then reviewing the whole branch.
draw.io Architecture Diagramming
HoangNguyen0403/agent-skills-standard
Draws architecture diagrams as editable draw.io files from a JSON spec, with a fixed house style, one C4 level per diagram and evidence-tagged shapes.
Android Navigation 3 Guide
HoangNguyen0403/agent-skills-standard
Implements and migrates to Jetpack Navigation 3 in Compose: NavDisplay, typed route objects, a state-list back stack, deep links, multiple back stacks and dialog scenes.
Angular HttpClient Standards
HoangNguyen0403/agent-skills-standard
Sets rules for Angular HTTP code: functional interceptors, typed requests, services that own every call, and httpResource for reactive data loading in Angular 17+.
Angular Tooling
HoangNguyen0403/agent-skills-standard
Angular CLI usage, code generation, build configuration, and bundle optimization.
Common Code Review
HoangNguyen0403/agent-skills-standard
Conduct high-quality, persona-driven code reviews. An agent skill from HoangNguyen0403/agent-skills-standard.
Related
Works with
Categories
Questions about Golang Tooling
What does Golang Tooling do?
Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Golang Tooling is an agent skill from HoangNguyen0403/agent-skills-standard. Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet.
When should I use Golang Tooling?
Golang Tooling fits situations like: setting up Go tooling; running linters; integrating gopls with Claude Code.
How do I install Golang Tooling in Claude Code?
Run `npx skills add HoangNguyen0403/agent-skills-standard --skill golang-tooling -a claude-code`. Or copy the skill folder (skills/golang/golang-tooling in HoangNguyen0403/agent-skills-standard) into .claude/skills/golang-tooling in your project. Claude Code loads it when a task matches its description.
How do I install Golang Tooling in Codex?
Run `npx skills add HoangNguyen0403/agent-skills-standard --skill golang-tooling -a codex`. Or copy the skill folder (skills/golang/golang-tooling in HoangNguyen0403/agent-skills-standard) into .agents/skills/golang-tooling in your project. Codex loads it when a task matches its description.
Can I use Golang Tooling in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HoangNguyen0403/agent-skills-standard --skill golang-tooling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/golang-tooling, .gemini/skills/golang-tooling, .github/skills/golang-tooling and .opencode/skills/golang-tooling in your project.
What does Golang Tooling need to run?
Going by SKILL.md and its folder, Golang Tooling needs the command-line tools its instructions call (go).
Does Golang Tooling access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Golang Tooling safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Golang Tooling use?
Golang Tooling is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Golang Tooling use?
About 531 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 127 tokens, read only when the agent opens those files.
What are the alternatives to Golang Tooling?
Skills that share tags, products or a category with Golang Tooling: Go Pedantry (chromedp/chromedp, 13k stars), Golang Lint (context-labs/whip, 1.1k stars), Golang Code Style (unxed/f4, 244 stars) and Validate Agent Work (kryptamine/herdr-auto-title, 246 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Golang Tooling?
HoangNguyen0403 (a GitHub user) maintains it in HoangNguyen0403/agent-skills-standard, which has 572 GitHub stars. The repository holds 211 skills in this directory. The repository was last updated on October 9, 2026.
Source: HoangNguyen0403/agent-skills-standard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.