Golang Data Structures
v1.1.1Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/...
⭐ 0· 100·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 (Go data-structures) match the provided SKILL.md, references, and evals. Requiring the 'go' binary is reasonable for running examples/tests or using Go tooling. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md contains focused guidance about slices, maps, arrays, container packages, unsafe/weak pointers and generics. It does not instruct network calls or reading arbitrary system credentials. However the skill's allowed-tools include Read/Edit/Write and Bash (go/git/golangci-lint) which gives the agent discretion to read and modify workspace source and run Go commands; that is expected for a coding assistant but worth noting if you don't want it modifying your repo.
Install Mechanism
No install spec and no archives or external downloads — instruction-only skill (no code executed on install). This is the lowest-risk install profile.
Credentials
The skill requests no environment variables, secrets, or config paths. The documentation references Go toolchain and standard-library features only — no disproportionate credential access.
Persistence & Privilege
always:false (not force-included). disable-model-invocation:false (model may invoke autonomously), which is the platform default and not, by itself, a security concern here. The skill does not request system-wide config changes.
Assessment
This skill appears coherent and low-risk: it is an instruction-only Go reference that asks for no credentials and performs no installs. If you install it, be aware the agent is allowed to read/write workspace files and run Go tooling (go build/test/lint) — typical for a coding assistant but you should only enable it on codebases you trust. If you want tighter control, verify the specific SKILL.md content and references, and consider restricting file-edit or command execution permissions in the agent environment before allowing autonomous invocation.Like a lobster shell, security has layers — review code before you run it.
latestvk976awjagm4xd3xnm0b8s6h7qs83kyzh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🗃️ Clawdis
Binsgo
