cc-skills-golang: two of nine install routes install a different repository
🧑🎨 A collection of Golang agentic skills that works
At a glance
- What is it?
- cc-skills-golang is a set of on-demand instruction files that give a coding assistant Go-specific guidance, with per-skill token weights so a whole pack stays cheap until a skill triggers. Its table is sorted by a column the file never defines, one install route clones without pinning, and two of the nine documented routes point at a sibling repository instead of this one.
- Who is it for?
- cc-skills-golang fits someone whose assistant keeps giving generic Go advice and who wants house conventions loaded on demand rather than permanently. Verify four things before you install it.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 7 days ago.
- What is it written in?
- Mainly Go, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- samber/cc-skills-golang3,859 ★ · +627
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| samber/cc-skills-golang | 3.2k | 3.9k |
627 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Two of the nine routes install a sibling repository
The universal route installs this repository, and six of the eight client routes clone this repository. Two do not. The Codex block installs a different project entirely:
codex plugin add github:samber/cc-skillsIts update command names the same other project, and the manual fallback it offers clones that other project too. The Claude Code block has the same shape one step removed: it adds a marketplace belonging to the sibling project and then installs a plugin from it. The file does tell you the split earlier on, saying this repository is the language half and that workflow skills live in a separate plugin. The problem is that the two routes most likely to be followed by someone who does not read that paragraph install the workflow half. There is corroborating detail in the tree as well: this repository carries its own plugin manifest directory for Codex, which the documented Codex command never touches.
The table is sorted by a column the file never defines
Every skill row carries a column headed error rate gap, and the values are percentages with minus signs in front of them, running from the low twenties to the high fifties. Nothing in the visible file says what error rate, of what, measured how, or against which baseline. It is the most prominent column in the table, it is what the recommended rows appear to be ordered by, and it is the number a reader is most likely to quote. The repository root does contain a document whose name suggests it might explain a measurement, and the front page never points at it. So the differentiator between two skills that differ by thousands of tokens of guidance is a percentage nobody can evaluate from what is written.
The recommended block is not sorted by its own key
If the recommended rows are meant to be ordered by that percentage, they are not. The visible sequence runs from about forty percent down to thirty-seven, then jumps to fifty-three, drops to twenty-six, and later jumps to forty-three and to fifty-eight. So either the sort key is something else, or the ordering is stale, and a reader has no way to tell which. The token columns beside it are per-skill rather than cumulative, which is worth stating because the directory weights climb into five figures by the bottom of the recommended block and then drop back to four figures for the next set of rows. Read as a set, the table tells you the recommended skills are also among the heavier ones, without ever telling you what the ordering is.
The flagship command installs the thing the guide warns against
The skills section is explicit that the units are designed to reference each other, that one skill's conventions may live in another, and that installing only a subset gives a partial and potentially inconsistent view of the guidelines. It recommends installing all the general-purpose skills together. Then the universal install command's own second example installs one skill by name. So the most prominent install block in the file demonstrates precisely the partial install the section above it argues against. The example is not a throwaway either: the skill it names carries a main file of a couple of thousand tokens and a directory weighing close to twenty thousand, so pulling it alone brings in referenced files whose relationships to the absent skills are exactly what the warning is about.
Five routes are a bare clone with no pinning
Of the eight client routes, three go through a package or plugin command and five tell you to clone the repository into a discovery directory. None of the five pins a tag, a commit or a branch. Only one of them then says how to update, which is a pull inside the cloned directory. The rest leave you to work out that a plain fetch is how you refresh instruction files that your assistant is reading on every session. The directories themselves are all different, and one of them is shared: a generic agents directory is used by two of the eight clients, while the other six each have their own, giving seven distinct paths for the same content.
The recorded language is Go and there is no Go code
The repository is recorded as a Go project. It contains no Go code. What it contains is Markdown: instruction files, a citation file, an evaluation document, a review document, a contributor document and a set of rules. The language is almost certainly detected from the skill filenames, every one of which begins with the language name. That is harmless as metadata and actively misleading as a signal, because the useful question about this repository is how well the guidance holds up and how current it is, and neither is a function of the detected language. It also explains why the newest tag is six weeks behind the last commit: nothing here is built, so nothing forces a release when the content changes.
Four client manifests in three shapes, and a channel the README omits
The tree carries three plugin manifest directories, one each for the three clients that install by plugin, plus a single extension manifest file at the root for a fourth client. So four manifests expressed three different ways, with the one for the client whose documented command installs a different repository sitting in the repository that command does not install. There is also a shell script at the root for publishing to a distribution channel that appears nowhere in the documentation, which makes it a tenth route rather than one of the nine. And the content is split across two directories, one for skills and one for rules, so a reader cloning for the skills gets the rules directory without being told it exists or what is in it.
One skill's directory weighs exactly its main file
The file explains a three-tier cost model, which is the most useful engineering content in it. One weight is the description field from the front matter, and that one is always loaded so the assistant knows the skill exists. A second weight is the whole main file, loaded when the skill triggers. A third is everything in the skill's directory including the files it references. Most rows show the third number far above the second, which is the referenced material. One row shows them identical, meaning that skill has no auxiliary files at all while every other skill does. The legend also defines two statuses the table never uses, and the category diagram is cut off partway down, so the shape of the pack is only half shown.
Editorial conclusion
cc-skills-golang fits someone whose assistant keeps giving generic Go advice and who wants house conventions loaded on demand rather than permanently. Verify four things before you install it. Read the skills section's warning that installing a subset gives an inconsistent view, and note that the flagship one-line install command demonstrates exactly the single-skill install it warns against. Decide how you will keep it current, because five of the eight client routes are a bare clone with no pinning and only one documents how to update. Check which route your client uses, because two of the documented routes install a sibling repository instead of this one, and this repository carries a plugin manifest that one of them never reads. And treat the table's headline percentage as unverified, because the file never says what it measures.
Frequently asked questions
What is samber/cc-skills-golang?
A set of instruction files that give a coding assistant Go-specific guidance, loaded on demand so they do not permanently occupy the assistant's context. It covers language conventions, data structures, database access, design patterns, documentation, error handling, naming, refactoring, safety, testing, troubleshooting, security, benchmarking, concurrency, context handling, continuous integration, dependency work, linting, observability and performance, each with its own reference material.
How do I install the golang skills for a coding assistant?
The universal route runs a package command that adds the repository, either all skills or one named skill. Eight clients have their own sections: three install by plugin or extension command and five tell you to clone the repository into a client-specific discovery directory. Two of those eight, for two named clients, install a sibling repository rather than this one.
What does the error rate gap column in the golang skills table mean?
The file does not say. Each row carries a percentage in that column, ranging from the low twenties to the high fifties, and nothing in the visible text defines what error rate is being measured, on what, by what method, or against which baseline. It is the column the recommended rows appear to be ordered by, and the ordering is not monotonic.
Can I install only some of the golang skills?
Technically yes, the install command takes a single skill by name, and the file says the units reference each other on purpose. But the skills section also says that installing only a subset gives a partial and potentially inconsistent view of the guidelines and recommends installing all the general-purpose skills together. The example single-skill install is the thing that section warns against.
What Golang skills does the samber pack cover for an assistant?
The visible table lists twenty-four: code style, data structures, database, design patterns, documentation, error handling, how-to, modernize, naming, refactoring, safety, testing, troubleshooting, security, benchmark, cli, concurrency, context, continuous integration, dependency injection, dependency management, structs and interfaces, lint, observability and performance, and the table is cut off after that. Each carries flags for whether a command is available, whether the assistant is told to think harder, and whether the settings are overridable.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/samber-cc-skills-golang)Star history chart for your README
[](https://hysenlabs.com/projects/samber-cc-skills-golang)Was this useful?