Golang Code Style
v1.1.1Golang code style, formatting and conventions. Use when writing code, reviewing style, configuring linters, writing comments, or establishing project standards.
⭐ 0· 141·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
Name/description match the content: the SKILL.md is a Go code-style guide. The metadata declares the 'go' binary as required — reasonable if the agent will run go tools (gofmt/govet/etc.), but not strictly necessary for a purely prose style guide. This is a minor mismatch worth noting.
Instruction Scope
Instructions are style guidelines and examples only. The SKILL.md does not direct the agent to read unrelated files, exfiltrate data, call external endpoints, or access environment variables beyond the declared requirements.
Install Mechanism
No install spec and no code files — instruction-only. Nothing will be downloaded or written to disk by the skill itself.
Credentials
The skill declares no environment variables, secrets, or config paths. It only lists a required binary ('go'), which is proportionate to its possible need to run Go tooling.
Persistence & Privilege
always:false and no special privileges requested. The skill can be invoked autonomously by the agent (platform default) but does not request permanent presence or to modify other skills/config.
Assessment
This skill is largely low-risk: it's an instruction-only Go style guide and does not request secrets or install code. Note that the skill metadata and allowed-tools indicate the agent may run 'go' and linters (e.g., golangci-lint, git) against your workspace — if you don't want the agent to execute formatting/linting commands locally, restrict tool access or review the agent's permissions before enabling the skill. Also confirm you trust the source/homepage and the versions of any tools the agent will use, since the skill itself doesn't pin or install those tools.Like a lobster shell, security has layers — review code before you run it.
latestvk97b3c7vjcj06w2f62aqbypdwx83eb3y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎨 Clawdis
Binsgo
