ClawHub

Golang Documentation

v1.1.2

Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and...

⭐ 0· 109·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, templates, and references all describe Go documentation work and the only declared required binary is `go`, which is appropriate. The skill's allowed tools include git and golangci-lint, and templates reference running linters and tests — this is consistent with documentation/validation workflows, though the metadata does not declare those extra binaries as required (minor inconsistency).
ℹ
Instruction Scope
SKILL.md explicitly instructs the agent to read the repo, edit/write documentation files, run validations (e.g., `go build`, `go test`, `golangci-lint` in templates), and use up to 5 parallel sub-agents. Those actions are reasonable for producing/validating documentation, but executing build/test commands will run repository code (which can execute arbitrary code). The skill does not request unrelated secrets or system paths, but users should be aware of the runtime risk of executing untrusted code/tests.
✓
Install Mechanism
Instruction-only skill with no install spec and no downloads — low install risk.
✓
Credentials
The skill declares no required environment variables or credentials. Documentation templates show example env var names (e.g., MYTOOL_DB_URL) for guidance only. There is no request for unrelated secrets.
ℹ
Persistence & Privilege
always:false (normal). The skill permits autonomous invocation (platform default) and encourages using the Agent and WebFetch tools. That is coherent for a documentation assistant (parallel sub-agents, web lookups), but gives the agent the ability to perform network requests and spawn sub-agents — consider limiting autonomous use or network access if you need stronger controls.
Assessment
This skill appears to do what it says: generate and review Go project documentation and templates. Before enabling it with autonomous access, consider: (1) running it in a sandbox or on a fork/branch because its instructions may run `go build`/`go test` and linters (these execute repository code); (2) whether you want the agent to be allowed to write/commit changes or only propose edits (review diffs first); (3) installing or making available tools referenced in templates (golangci-lint, git) since metadata only requires `go`; and (4) restricting or auditing network access (WebFetch/Agent) if your environment forbids automated outbound requests. If you need me to produce a minimal set of policy recommendations (e.g., CI job vs local dev, devcontainer setup, or sandboxing commands), tell me your security constraints and I will suggest concrete controls.

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

latestvk97968h29tqmy62938c4vx88gx83zznz

License

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

Runtime requirements

📝 Clawdis
Binsgo

Comments