Golang Grpc
v1.1.3Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging...
⭐ 0· 139·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 (gRPC best practices) align with the declared requirements: go and protoc are sensible prerequisites and the install uses the well-known Homebrew 'protobuf' formula to provide protoc. No unrelated binaries, env vars, or config paths are requested.
Instruction Scope
SKILL.md contains guidance, examples, and references limited to designing, implementing, reviewing, and testing Go gRPC services. It does not instruct reading unrelated system files, harvesting credentials, or posting data to external endpoints. It does grant the agent permission to read/edit/write project files (expected for a coding assistant) — review any file changes before committing.
Install Mechanism
Install spec uses a known package manager (brew) and the official 'protobuf' formula to provide protoc. This is a low-risk, standard install; no arbitrary downloads or archive extraction are present.
Credentials
The skill requests no environment variables or credentials. The lack of secret requirements is proportionate to a documentation/style-guide skill.
Persistence & Privilege
always is false and the skill does not request elevated or persistent system privileges. Model invocation is allowed (the platform default) — combined with no broad credential access, this is reasonable for a coding assistant. Note: the skill is marked user-invocable: false, meaning it is intended for autonomous agent use only.
Assessment
This skill appears to be a documentation / code-guidance pack for Go gRPC and is internally consistent. Before enabling or letting an agent run it: 1) confirm you trust the agent to edit repository files (the skill allows read/write privileges to project code); 2) be aware the install step will run brew install protobuf (protoc) if the platform performs installs — ensure brew is acceptable on your system; 3) review any automated code changes suggested by the agent (and run tests) before merging; and 4) if you need the skill to not run autonomously, disable or restrict agent access because autonomous invocation is allowed by default. If you want extra assurance, request the skill author/source or run it in an isolated environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk972491fcpzm2eh9m5qe5tfdg583zz2y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🌐 Clawdis
Binsgo, protoc
Install
Homebrew
Bins: protoc
brew install protobuf