samber/do Dependency Injection
Type-safe dependency injection in Go with samber/do — containers, scopes, lifecycle
- What
- Type-safe dependency injection in Go with samber/do — containers, scopes, lifecycle
- Cost
- Free
- Needs
- a Go project with the Go toolchain installed; the samber/do library as a dependency
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a guide to samber's own do library (github.com/samber/do): type-safe dependency injection for Go based on generics — service containers, lifecycle management, scopes, health checks, graceful shutdown, and module organization. Keep the container at the composition root, depend on interfaces not concrete types, treat provider errors as first-class failures. This is one of four library guides by @samber for his own Go libraries (alongside oops for structured errors, hot for in-memory caching, and ro for reactive streams) — self-promotional in subject, but substantial (236 lines) and genuinely useful when adopting the library. By @samber, listed here with credit to its creator. Honest caveats: requires a Go project importing samber/do; it documents one specific library's API — not a general DI-pattern guide. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
samber/do Dependency Injection is a free Muse skill guiding type-safe dependency injection in Go with samber/do, the generics-based library covering service containers, lifecycle management, scopes, health checks, graceful shutdown and module organization. It teaches keeping the container at the composition root, depending on interfaces rather than concrete types, and treating provider errors as first-class failures, for projects already importing samber/do.
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 project with the Go toolchain installed; the samber/do library as a dependency Install "samber/do Dependency Injection" for me. Type-safe dependency injection in Go with samber/do — containers, scopes, lifecycle Repository: https://raw.githubusercontent.com/samber/cc-skills-golang/8e899e20ff0cd4dc524af3993e4c62d8ee8c5717/skills/golang-samber-do/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 for the samber-golang-samber-do skill from the repository 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 "samber-golang-samber-do". 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.
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.