ClawHub

Golang Design Patterns

v1.1.2

Idiomatic Golang design patterns — functional options, constructors, error flow and cascading, resource management and lifecycle, graceful shutdown, resilien...

⭐ 1· 186·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 (Go design patterns) align with the SKILL.md and the shipped reference documents. Required binary is only 'go', which is proportional to the purpose. No extraneous credentials, binaries, or config paths are requested.
✓
Instruction Scope
SKILL.md instructs the agent to provide design guidance and to review project code for Go-specific patterns (init() use, resource lifecycles, timeouts, streaming, etc.). That scope is appropriate for a design/review skill and does not direct the agent to read or exfiltrate unrelated system files or secrets.
✓
Install Mechanism
Instruction-only skill with no install spec and no archives or remote downloads. Nothing will be written to disk by an installer; this is low-risk.
✓
Credentials
The skill declares no environment variables, no credentials, and no config paths. That matches the described functionality (guidance and code review) and is proportionate.
✓
Persistence & Privilege
always:false and no install behavior means the skill does not demand permanent or elevated presence. Allowed tools include file read/write and shell commands, which are necessary for code review and suggested refactors but should be used with usual caution.
Assessment
This skill appears coherent and focused on Go design patterns. Before installing: (1) Verify you trust the skill owner/homepage (the registry lists a GitHub homepage). (2) Note that the skill's allowed tools include reading and editing files and running go-related commands — if you want to restrict risk, limit the agent's ability to run shell/git/go or to write files. (3) Because it can review code, run it in a sandbox or on a non-sensitive repo first. (4) No credentials are requested, so do not provide any secrets; if the skill later asks for environment variables, treat that as unexpected and re-evaluate. (5) If you need stricter control, disable autonomous invocation for this skill in your agent's policy.

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

latestvk97f5vz2n83ds4zn3q4e0d7ym583zsmp

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🏗️ Clawdis
Binsgo

Comments