Golang CLI Development
Build Go CLI tools that feel native — cobra/viper stack, flags, exit codes, completions
- What
- Build Go CLI tools that feel native — cobra/viper stack, flags, exit codes, completions
- Cost
- Free
- Needs
- a Go project with the Go toolchain installed
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a Go CLI engineering guide with build, extend, and review modes: command structure and subcommands, flag handling and configuration layering, version embedding, exit codes, I/O patterns, signal handling, shell completion, argument validation, and CLI unit testing. Defaults to the Cobra + Viper stack (the combination powering kubectl and docker), with pointers to the dedicated samber-golang-spf13-viper skill for viper-specific APIs. Builds tools that feel native to the Unix shell — composable, scriptable, and predictable under automation. By @samber, listed here with credit to its creator. Honest caveats: requires a Go project; it's engineering guidance with review checklists, not a scaffolding generator — it won't bootstrap the CLI for you. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Go project with the Go toolchain installed Install "Golang CLI Development" for me. Build Go CLI tools that feel native — cobra/viper stack, flags, exit codes, completions Repository: https://github.com/samber/cc-skills-golang/blob/main/skills/golang-cli/SKILL.md 1. Fetch the SKILL.md file for the samber-golang-cli skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "samber-golang-cli". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.