ClawHub

Golang Cli

v1.1.2

Golang CLI application development. Use when building, modifying, or reviewing a Go CLI tool — especially for command structure, flag handling, configuration...

⭐ 0· 121·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 match the content: SKILL.md is Go CLI best-practices and the bundle contains many example Cobra/Viper source files. The only required binary is 'go', which is appropriate.
ℹ
Instruction Scope
SKILL.md focuses on building/reviewing Go CLIs and the examples show config, env, file watching, signal handling, exit codes, completion, etc. This is in-scope. One noteworthy behavior: examples use viper.AutomaticEnv() and read $HOME for config files — expected for CLI config guidance but it means code examples will bind environment variables automatically if used verbatim, so reviewers should be aware of that side effect.
✓
Install Mechanism
Instruction-only skill with no install spec and no downloads; lowest install risk.
✓
Credentials
The skill declares no required environment variables or credentials. The SKILL.md recommends Viper for env config (including AutomaticEnv) which is reasonable for the described purpose but may cause inadvertent env var binding if example code is used without review.
✓
Persistence & Privilege
always:false and no config paths/credential access. The skill allows normal autonomous invocation (disable-model-invocation:false), which is the platform default — not a concern here by itself.
Assessment
This skill appears coherent and appropriate for helping build or review Go CLI apps. Before using examples in production: (1) review any example code you copy-paste (especially config init that uses viper.AutomaticEnv()) so it doesn't unintentionally bind or expose environment variables from your environment; (2) note examples read $HOME and look for config files — ensure paths and permissions are acceptable for your use; (3) the skill can be invoked by the agent (normal behavior) and may run allowed tools (git, go, linters) if the agent has those permissions — only enable it for agents you trust.

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

latestvk97czmexz03ysgx7rk1qcmh3d983w92f

License

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

Runtime requirements

💻 Clawdis
Binsgo

Comments