← Search

Golang Testing Best Practices Skill for Muse
Productivity 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 8e899e2
Install test only, on the date shown. This does not guarantee the code is safe.
🔎 Install prompt analysis · 2026-10-13 : installs packages
⚙ Needs: the Go toolchain installed on your machine…

Golang Testing Best Practices Skill for Muse

Production-ready Go tests: table-driven, parallel, leak-free

At a glance
What
Production-ready Go tests: table-driven, parallel, leak-free
Cost
Free
Needs
the Go toolchain installed on your machine; gotests installed via `go install github.com/cweill/gotests/gotests@latest`; a Go project whose tests you want to write, review, or audit. No API keys.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Golang Testing Best Practices Skill for Muse is a free open-source skill presenting a senior Go engineer persona for production-ready tests. It offers four modes: write, review, audit, and debug, built on an opinionated core of table-driven tests with named subtests, integration tests behind boundaries, and attention to goroutine and race issues throughout the test suite.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 8e899e2

Step 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: the Go toolchain installed on your machine; gotests installed via `go install github.com/cweill/gotests/gotests@latest`; a Go project whose tests you want to write, review, or audit. No API keys. Install "Golang Testing Best Practices Skill for Muse" for me. A senior Go engineer persona for production-ready tests: four modes (write, review, audit, debug), opinionated best practices (table-driven tests with named subtests, build tags for integration tests, t.Parallel, goleak goroutine-leak detection, coverage as gap finder), the testify assert-scope pitfall, modern idioms (testing/synctest, t.ArtifactDir), and a dense go test quick-reference. Repository: https://raw.githubusercontent.com/samber/cc-skills-golang/8e899e20ff0cd4dc524af3993e4c62d8ee8c5717/skills/golang-testing/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 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 "golang-testing". 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 gotests, and point it at the Go package to test). 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.

🔒 Security, provenance and what this touches
🧭 What this touches
  • It can download and install software packages.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 8e899e2 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Install prompt analysis · 2026-10-13 : installs packages
What the scan found — excerpts from the install prompt
  • installs packages — Prerequisites: the Go toolchain installed on your machine; gotests installed via `go install github.com/cweill · Prérequis : la toolchain Go installée sur votre machine ; gotests installé via `go install github.com/cweill/g
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
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
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

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 : installs packages

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.