Golang Samber Do

v1.1.3

Implements dependency injection in Golang using samber/do. Apply this skill when working with dependency injection, setting up service containers, managing s...

0· 106·0 current·0 all-time
bySamuel Berthe@samber
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description say 'dependency injection with samber/do' and the SKILL.md only describes how to use that library. The only declared runtime requirement is the 'go' binary which is appropriate for a Go-focused coding/teaching skill.
Instruction Scope
The instructions are limited to installing and using github.com/samber/do/v2, registering providers, scopes, testing patterns, health checks, and graceful shutdown. They do not instruct reading unrelated files, harvesting environment variables, or sending project data to external endpoints beyond normal library documentation links and a go get command.
Install Mechanism
This is an instruction-only skill (no install spec). The SKILL.md recommends running 'go get -u github.com/samber/do/v2' which is the expected way to add the library; nothing is downloaded from obscure URLs or written by the skill itself.
Credentials
The skill requests no environment variables, no credentials, and no config paths. That is proportionate for a documentation/guide skill about a Go DI library.
Persistence & Privilege
always:false and no install step means the skill does not request permanent presence or elevated privileges. disable-model-invocation is false (agent may invoke autonomously) but there are no additional red flags that amplify risk.
Assessment
This skill is a documentation-style, instruction-only helper for using samber/do v2 and appears internally consistent. Things to consider before enabling: (1) The SKILL.md suggests running 'go get -u', which will modify module files (go.mod/go.sum) in your project—run it in a safe branch or sandbox if you're cautious. (2) The allowed tools include web fetch and git commands; these are reasonable for a coding assistant but will allow the agent to access docs/repos—ensure you trust the agent session and that no sensitive data is exposed. (3) The skill enforces v2 usage (good); verify your project is ready for the v2 API before applying changes. Overall the skill is coherent with its stated purpose and does not request unrelated credentials or system access.

Like a lobster shell, security has layers — review code before you run it.

latestvk97096p4aw8r5adgxds1ehhafn840zqm

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

💉 Clawdis
Binsgo

Comments