Golang Structs Interfaces

v1.1.1

Golang struct and interface design patterns — composition, embedding, type assertions, type switches, interface segregation, dependency injection via interfa...

0· 98·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
The skill's name and description match the SKILL.md content: Go struct/interface design guidance. Requiring the go binary is reasonable (the agent may compile or run examples), and the allowed tools (edit/read/write, bash with go, lint, git) are proportionate for a coding helper.
Instruction Scope
SKILL.md contains only design guidance and examples; it does not instruct the agent to read unrelated system files, exfiltrate secrets, or call external endpoints. The allowed-tools permit reading and editing code files which is appropriate for a coding assistance skill, but this means the agent could modify local source — expected for this use case.
Install Mechanism
No install spec and no archived downloads are present. This is instruction-only, so nothing is written to disk by an installer step — lowest-risk installation footprint.
Credentials
The skill declares no environment variables, no credentials, and no config paths. That is appropriate for a documentation/style guidance skill and does not request any unrelated secrets or access.
Persistence & Privilege
always:false and no special persistence is requested. The skill is allowed to be invoked autonomously by the agent (disable-model-invocation:false), which is the platform default; there are no indications it modifies other skills or system-wide settings.
Assessment
This skill is a coherent Go design guide and appears safe from a permissions/credential perspective. It does request the go tool and grants the agent file read/write and the ability to run go/lint/git commands — which is appropriate for editing/validating code but means the agent could modify local source or run code. Only install/use it if you trust the agent to operate on your codebase and you are comfortable with it running the go toolchain in the environment. If you need stricter controls, limit file access or run the agent in a sandboxed environment; otherwise this skill looks benign and aligned with its stated purpose.

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

latestvk972t55fj7bvy509jhkfsghwkx83rerm

License

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

Runtime requirements

🧩 Clawdis
Binsgo

Comments