Golang Dependency Injection
v1.1.2Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management...
⭐ 0· 125·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
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the SKILL.md and reference files. Required binary (go) and the listed allowed tools (reading/writing code, running go commands, fetching docs) are reasonable for a DI guidance and code‑generation/refactor assistant.
Instruction Scope
The SKILL.md focuses on architecture guidance, example code, and automated/refactor modes that will analyze project source (it explicitly mentions using parallel sub-agents to find globals/init() and map dependencies). That implies the agent will read and edit repository files and run go commands — which is expected for this skill, but you should expect it to access your codebase files when invoked.
Install Mechanism
Instruction-only skill with no install steps and no external downloads; lowest-risk install profile.
Credentials
No environment variables, credentials, or config paths are requested. The skill's allowed tools permit repository/file access and web fetches; those are appropriate for analyzing and generating Go code.
Persistence & Privilege
always is false (not force-included). disable-model-invocation is false (normal — agent may call it autonomously). The skill does not request persistent system-wide privileges or modify other skills' configs.
Assessment
This skill appears to do what it says: guide DI decisions and generate or refactor Go wiring. Before enabling it, be aware it will read and (if invoked with write access) may modify your codebase and run go commands. It does not request credentials or perform network downloads as part of an install, but it is allowed to fetch documentation/web resources. Grant it only the repository/file access you are comfortable with and avoid supplying secrets or broad system credentials. If you want to be extra cautious, run it with read-only access first or review any generated patches before applying them.Like a lobster shell, security has layers — review code before you run it.
latestvk97bm48vv4bcp4tzd6h0ew7q6x83yeb6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔌 Clawdis
Binsgo