Best AI Agent Skills for Go Developers in 2026

Search any skills directory for "Go" and you'll get thirty results. Roughly four of them are agent skills. The rest are Go projects that happened to get indexed: a microservices framework with 33,000 stars, a generics library, a CLI scaffolder, a list of books.

That gap matters, because installing a "skill" that's a web framework does nothing for your agent. It just sits there.

Here's what exists for Go developers as of 3 August 2026, verified against each repository rather than against a directory listing.

The real Go agent skills

Star counts came from the GitHub API on 3 August 2026. Everything else came from each repo's own README.

samber/cc-skills-golang is the one to install first

This is the only Go skill pack with real weight behind it, and it's maintained by Samuel Berthe, whose lo generics library most Go teams already have in their dependency tree.

The pack ships more than 30 skills grouped into code quality (error handling, naming, safety, security, lint), architecture (concurrency, context, data structures, database access, design patterns, refactoring), QA and performance (testing, benchmarking, observability, troubleshooting), project setup (CLI, CI/CD, dependencies, project layout), and framework coverage for gRPC, GraphQL, Swagger, Cobra, Viper, Wire, Dig, and Fx. There are also skills for the author's own libraries and for testify.

Two things make it useful in practice rather than merely long. The concurrency and context skills encode the things Go reviewers flag: goroutine leaks, unpropagated cancellation, the mistakes that pass tests and fail at 3am. And the skills are granular, so you can install one instead of all 30 and keep your context budget intact.

Install commands, quoted from the repo:

• npx skills add https://github.com/samber/cc-skills-golang --all
• npx skills add https://github.com/samber/cc-skills-golang --skill golang-performance

For Claude Code specifically, the README documents a two-step marketplace flow:

• /plugin marketplace add samber/cc
• /plugin install cc-skills-golang@samber

Note the marketplace is samber/cc, not the skill repo itself. Getting that wrong is the most likely reason your install fails.

Cursor and Copilot users clone into their own skills directory instead:

• git clone https://github.com/samber/cc-skills-golang.git ~/.cursor/skills/cc-skills-golang

cxuu/golang-skills is the better second install

Twenty skills built around published style guidance from Google and Uber, covering go-code-review, go-testing, go-error-handling, go-interfaces, go-logging, and go-generics, among others. Apache-2.0 licensed, with bundled upstream snapshots keeping their original licenses in a third-party notices file. That's a more careful licensing posture than most community skill repos bother with.

The overlap with cc-skills-golang is real but not total. Where samber's pack leans toward framework and library specifics, this one leans toward review-time judgment: is this interface too wide, is this error wrapped correctly, does this generic need to be generic at all.

Documented installs:

• npx skills add cxuu/golang-skills --all
• /plugin marketplace add cxuu/golang-skills
• /plugin install golang-skills@cxuu-golang-skills

Cursor users get a native remote rule instead of a clone: Settings, then Rules, Add Rule, Remote Rule, pointing at the repo URL.

If you run both packs at once, expect duplicated guidance on error handling and testing. Pick one as your default and pull individual skills from the other.

Two narrow picks

gfargo/tui-design-skill covers terminal UI design across Go, Rust, Python, and TypeScript. If you're building anything with Bubble Tea, this is more useful than its 16 stars suggest, because TUI layout is exactly the kind of thing models get plausibly wrong.

praetorian-inc/reduce-golang-detections-skill is a security research skill for reducing detection rates on compiled Go binaries through PE analysis. It's from Praetorian, a legitimate security firm, and it exists for red team work. Install it if that's your job and skip it otherwise.

What the directories are calling a Go skill that isn't one

This is worth spelling out, because it's the single biggest waste of time in this category.

zeromicro/go-zero has 33,227 stars and is listed in skills directories including ours. It's a cloud-native microservices framework with a code generation CLI. Excellent software. Not a skill.

Same story for samber/lo (21,406 stars, a Lodash-style generics library), go-nunu/nunu (a CLI scaffolder for Go apps), MadAppGang/dingo (a meta-language adding Result types and pattern matching to Go), rulego/rulego (a rule engine), ankorstore/yokai (a backend framework), and dariubs/GoBooks (a reading list). metoro-io/mcp-golang is a good MCP server SDK for Go, which makes it a way to build agent tooling, not a skill you install into an agent.

The test is simple: does the repo contain a SKILL.md, or a plugin manifest that points at one? If it's just a Go library, an agent can already read its docs. Installing it as a skill accomplishes nothing except spending context.

The install command that doesn't exist

You will see claude skill add owner/repo published on skill directories, including in our own database's install field. It is not a real command. It appears nowhere in the official Claude Code skills documentation, and running it produces an error.

The install paths that do work:

• /plugin marketplace add <owner/repo> followed by /plugin install <name>@<marketplace>, from inside a session
• npx skills add <repo>, which several of the repos above document directly
• A manual clone into ~/.claude/skills/<name>/ with a SKILL.md at the root

Take the command from the repository's README every time. Directory listings, ours included, generate that field programmatically and get it wrong at scale.

Security checks before you install

A skill is instructions your agent will follow, and in packs like these it can also include scripts. Treat it like a dependency, not a bookmark.

Read the SKILL.md files before installing, not after. Skim for anything that instructs the agent to fetch remote content at runtime or to run a command against your environment. Check the last push date, since a Go skill written before generics landed in the language will teach patterns your team abandoned years ago. Check the license, because Apache-2.0 and MIT are fine while an unstated license in a corporate repo is a problem for someone in legal.

Prefer packs where you can install one skill rather than all of them. Both leading options here support that, and the smaller your installed surface, the less there is to audit.

For the broader picture on how skills differ from other extension points, see our breakdown of agent skills vs subagents vs hooks. If you work across stacks, the same analysis for backend frameworks and for Android and Kotlin covers the neighbouring ecosystems.

Where this category stands

Go is underserved compared to TypeScript or Python, and the numbers say so: one pack above 2,000 stars and a long tail below 150. Part of that is Go's culture. The language already has gofmt, go vet, and a strong convention set, so a lot of what skills provide elsewhere is enforced by tooling here.

That makes the remaining gap narrow but real. Concurrency correctness, context propagation, and interface design are the places Go code goes wrong, and they're judgment calls no linter catches. Both leading packs target exactly those. That's a good sign about the people writing them.

If you install nothing else, install the concurrency and error-handling skills from samber's pack and stop there. Then browse our developer tools list for the surrounding tooling.

FAQ

What is the best Claude Code skill for Go developers?

samber/cc-skills-golang, at 2,833 stars and 30-plus skills covering concurrency, error handling, testing, observability, and framework-specific guidance for gRPC, Cobra, Viper, Wire, and Fx. It's MIT licensed and was last pushed on 1 August 2026.

Why do skill directories list Go frameworks as skills?

Because they index repositories by topic rather than by structure. go-zero, lo, nunu, and GoBooks all appear as Go skills in multiple directories and none of them contain a SKILL.md. Check for a SKILL.md or a plugin manifest before installing anything.

Does claude skill add work?

No. That command does not appear in the official Claude Code skills documentation and returns an error. Use the plugin marketplace flow, npx skills add, or clone the skill into a folder under your skills directory with a SKILL.md at its root.

Can I install both major Go skill packs together?

Yes, but they overlap on error handling and testing guidance, which wastes context and can produce conflicting advice. Pick one as your baseline and install individual skills from the other. Both support single-skill installation.

Are there official Go skills from the Go team?

No. Every option here is community or third-party maintained. The closest thing to authoritative content is cxuu/golang-skills, which encodes published style guidance from Google and Uber rather than inventing its own conventions.