ClawHub

Golang Troubleshooting

v0.1.0

Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, or unexpected behavior in Go code....

⭐ 0· 80·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 claim Go debugging; declared required binaries are `go` and `dlv`, and the install spec installs Delve via `go install` from the Delve repo. These are exactly the tools a Go troubleshooting skill needs.
ℹ
Instruction Scope
SKILL.md stays focused on debugging methodology and concrete commands (go build/test, dlv, pprof, curl, git). It does suggest inspecting environment variables (e.g., `env | grep DATABASE` / `env | grep API_KEY`) and external endpoints for dependency checks, and has a 'codebase bug hunt' mode that may launch up to 5 parallel sub-agents. Inspecting env vars and contacting external services is expected for troubleshooting, but users should be aware the instructions ask the agent to read environment state and make network calls as part of diagnostics.
✓
Install Mechanism
Install uses `go install github.com/go-delve/delve/cmd/dlv@latest` which is the standard way to obtain `dlv` from the public Delve repository. This is an expected, traceable install path for the declared binary.
ℹ
Credentials
The skill declares no required environment variables (none in requires.env), yet the guidance explicitly recommends checking environment variables and refers to protecting pprof endpoints with credentials (PPROF_USERNAME/PPROF_PASSWORD). This is proportionate to debugging needs, but there's a minor mismatch between declared requirements (none) and the runtime guidance that will read environment state and potentially reference credentials if present.
✓
Persistence & Privilege
always is false; the skill does not request persistent system-wide privileges or modification of other skills. It does permit autonomous invocation (platform default), and the skill's ability to launch sub-agents (documented mode) is a functional choice rather than a covert privilege escalation.
Assessment
This skill is coherent for debugging Go programs: it requires `go` and `dlv` (it will install Delve via `go install`), and the instructions legitimately use tools like dlv, pprof, curl, git, and may read environment variables and contact external endpoints to reproduce or validate dependencies. Before installing: 1) ensure you want the agent to run debuggers and make network calls on your behalf (these can attach to local processes and fetch HTTP endpoints); 2) confirm `go` is already installed and you accept installing Delve into your Go bin; 3) be cautious when running in production — pprof endpoints can expose sensitive runtime data and the skill correctly recommends protecting them with auth; 4) if you plan to allow autonomous runs or the 'codebase bug hunt' mode, consider limiting the agent to a safe workspace or review each run, since the agent may inspect env vars and launch sub-agents. Overall the skill appears to do what it says.

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

latestvk97afcs8936d4x1216fxym5hns83h918

License

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

Runtime requirements

🔍 Clawdis
Binsgo, dlv

Install

Go
Bins: dlv

Comments