ClawHub

Golang Safety

v1.1.1

Defensive Golang coding to prevent panics, silent data corruption, and subtle runtime bugs. Use whenever writing or reviewing Go code that involves nil-prone...

⭐ 0· 87·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 are about defensive Go coding and the only declared runtime requirement is the 'go' binary; that is proportionate (linting, running examples/tests) and coherent with the skill's purpose.
✓
Instruction Scope
SKILL.md contains coding guidance, examples, and deep-dive references about nil, slices, maps, numeric conversions, and resource lifecycles; it does not instruct reading unrelated system files, exfiltrating data, or using credentials. Examples and evaluation prompts are internal to Go coding checks.
✓
Install Mechanism
There is no install spec and no code is written to disk by the skill itself (instruction-only), which minimizes install risk.
✓
Credentials
No environment variables, credentials, or config paths are requested. The declared binary requirement ('go') is appropriate for a Go safety skill.
✓
Persistence & Privilege
always is false and the skill does not request persistent or elevated privileges. The skill is allowed to be invoked autonomously (platform default), but it does not assert permanent presence or modify other skills.
Assessment
This skill is an instruction-only Go safety guide and is internally consistent with its stated purpose. Before installing, review the SKILL.md and reference files yourself to ensure the recommendations match your code style. Note the skill has access to run 'go' (and the tool permissions list includes bash wrappers like golangci-lint/git); if you permit autonomous invocation, the agent could run those tools against repositories the agent can access. If you want stricter control, keep autonomous invocation disabled or restrict the agent's repo/file access and review any commands it proposes before execution. Finally, verify the homepage/source if you need provenance beyond the provided docs.

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

latestvk971aagnkpdec9f7terav40f8h83p0xv

License

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

Runtime requirements

🛡️ Clawdis
Binsgo

Comments