Go Defensive Coding Skill for Muse
Defensive Go coding: kill nil panics and silent bugs.
- What
- Defensive Go coding: kill nil panics and silent bugs.
- Cost
- Free
- Needs
- a Go toolchain (go binary) on your machine; golangci-lint v2 optional (for the errcheck, forcetypeassert, nilerr, govet and staticcheck rules it cites). No API keys. Designed for Claude Code, Codex or a similar coding-agent harness, on projects using Golang.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Teaches Muse defensive Go coding: nil-interface traps (a typed nil pointer is not == nil), nil map writes, append backing-array aliasing, silent int64→int32 truncation, float == comparison, defer inside loops, goroutine and resource lifecycle, defensive copies of slices and maps, and zero-value design — each rule shown as a dangerous/good code pair. Expects a Go project and optionally golangci-lint for the errcheck/forcetypeassert/nilerr/govet/staticcheck rules it cites. Discovered via skills.sh. Honest note: it is prevention, not debugging — it explicitly hands off concurrency design, exploitable vulnerabilities, and failing-program diagnosis to sibling skills in the same repo (golang-concurrency, golang-security, golang-troubleshooting) that are not included here, so some sections point outward. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Curated by Skill Harbor — free, open-source skill (MIT) by @samber.
Version:
Quick answer
Go Defensive Coding Skill for Muse is a free open-source skill that teaches defensive Go coding through dangerous-versus-good code pairs. It covers nil-interface traps, nil map writes, append backing-array aliasing, silent int64-to-int32 truncation, float equality comparison, defer inside loops, goroutine and resource lifecycle, defensive copies, and zero-value design.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 8e899e2Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Go toolchain (go binary) on your machine; golangci-lint v2 optional (for the errcheck, forcetypeassert, nilerr, govet and staticcheck rules it cites). No API keys. Designed for Claude Code, Codex or a similar coding-agent harness, on projects using Golang. Install "Go Defensive Coding Skill for Muse" for me. Teaches defensive Go coding — nil-interface traps, nil map/slice/channel behavior, append backing-array aliasing, silent numeric conversion truncation, float comparison, defer in loops, defensive copies, sync.Once lazy init, and zero-value design — each rule as a dangerous/good code pair. Repository: https://raw.githubusercontent.com/samber/cc-skills-golang/8e899e20ff0cd4dc524af3993e4c62d8ee8c5717/skills/golang-safety/SKILL.md Pinned version: install the code at commit 8e899e20ff0cd4dc524af3993e4c62d8ee8c5717 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files: references/) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and references 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 "golang-safety". 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. install the go toolchain and optionally golangci-lint if not already present). 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. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 8e899e2 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.