Go Skills plugin
Seven Go skills from the creator of Cobra and Hugo: idiomatic style, CLI design, releases, Wails, file operations and afero tests
- 705 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- Instructions only: the skills run nothing on their own
- They read project files the agent already sees
Install
- Works in
Manual install
/plugin marketplace add spf13/go-skillsAdds the marketplace with seven skills.
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Instructions only: the skills run nothing on their own
- They read project files the agent already sees
This is third-party code. Review the repository files before installing.
What it does
Go Skills is a set of seven skills for Claude Code published as a plugin marketplace. The `go` skill sets the rules of idiomatic Go: package design, errors, interfaces, concurrency, tests and project layout. `cobra-viper` covers CLI architecture with Cobra and Viper, configured through environment variables. `go-spec-reviewer` reviews a design document before any code exists, and `go-release` runs releases through semantic versioning and GoReleaser. The remaining skills cover narrow libraries. `wails` tells the incompatible Wails v2 and v3 APIs apart so the agent stops mixing them in one project. `fileflow-pathologize` handles cross-filesystem moves and copies and cleans paths for OS limits. `afero` shows how to put the filesystem behind an interface and test code in memory. Each skill installs with its own `/plugin install` command. In other agents (Copilot, Cursor) the skill folders are linked into `~/.agents/skills`.
Who it is for. Go developers tired of telling Claude Code that Java-style `service/` and `repository/` layers do not belong in Go, and teams that ship CLIs built on Cobra.
Good fit when
- The agent produces an `internal/` tree with five layers while the project needs a flat layout by domain
- A new CLI on Cobra and Viper whose configuration must come from environment variables and be tested in memory
- A Go design document waits for review before any code, while fixes are still cheap
- A library is about to ship and breaking API changes need finding and `Deprecated:` notes
- A desktop app on Wails where the v2 and v3 APIs are easy to mix up
Not a fit when
- The project is not written in Go: the skills are entirely about that language
- The team deliberately uses layers and mock frameworks, which the skills argue against
- An old Claude Code build is installed: on 2.1.94 the plugin installs but the skill never registers
Example request
Install the go skill from go-skills and rework this project's package layout into a flat layout by domainLimitations
The skills need Claude Code with plugin and marketplace support: the author verified build 2.1.275, while on 2.1.94 the plugin installs but the skill never registers. The rules reflect one author's opinion: flat layout by domain, standard library over frameworks, channels before mutexes. A team with an established layered architecture will have to ignore part of the advice. The `wails` skill covers v2 and the v3 alpha, and the v3 API can still change. In other agents the skills work as instructions from `~/.agents/skills` without the author testing every version.
How to disable. `/plugin uninstall go@go-skills` removes the skill, and the other names go in the same place. `/plugin marketplace remove go-skills` drops the marketplace. In other agents, delete the link from `~/.agents/skills`.
FAQ
How do I install Go Skills in Claude Code?
Add the marketplace with `/plugin marketplace add spf13/go-skills`, then install a skill with `/plugin install go@go-skills`. For the others replace `go` with the name from the repository table.
Which skill should I install first?
The `go` skill. The author calls it the one to read first, and the others add CLI, release, Wails and file work.
Do the skills work in Cursor or Copilot?
Yes, as skill folders. Link the skill folder into `~/.agents/skills` and restart the editor.
How does `go-spec-reviewer` differ from a normal code review?
It reads a design document before code exists and looks for over-engineering, missing error paths and interface misuse while changes are cheap.
Why does the plugin install but the skill never fires?
Claude Code 2.1.94 behaves this way: the plugin registers without its skill. The author verified 2.1.275, so update the build.
Discussion
No questions or reviews yet.
Related
PluginsThirty-five Go skills that an agent loads on demand: errors, goroutines, testing, architecture and code review.
A skills library for Claude Code, Cursor and Codex: team code review, TDD, stacked PRs and repository readiness scoring
15 skills for Claude Code and Codex: Laravel, Docker, UI, debugging, tests and docs in four ready plugin bundles
19 skills for Claude Code, Codex and Antigravity CLI: Grok and Exa search, Context7 docs, Serena and task hand-offs between agents
Over 1,100 ready-made skills for Claude Code, Codex, Gemini CLI and Cursor, plus an MCP server that picks a skill for the task
Catalog of 46 versioned skills for code review, releases, CI and landing pages, installed as the lstack plugin or through npx.
README in short
The README lists seven Go skills published as a Claude Code plugin marketplace, with an install command for each. It then covers installation in Claude Code and in other agents, verification through `/plugin` and the Claude Code version requirement. The page closes with the author's reasoning: language models default to Java-style Go, and the skills steer them back to the standard library and a flat structure.