Go Web Expert

v2.3.0

Comprehensive Go web development persona enforcing zero global state, explicit error handling, input validation, testability, and documentation conventions....

0· 73·0 current·0 all-time
byKevin Anderson@anderskev
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 (Go web dev persona) match the content: an opinionated set of conventions, examples, and references for writing/testable Go web handlers. It requests no binaries, env vars, or platform installs that would be unrelated to this purpose.
Instruction Scope
SKILL.md and reference files contain coding rules, examples, and testing/validation guidance only. They do not instruct the agent to read host files, access environment variables, call external endpoints, or exfiltrate data. The instructions are opinionated but stay within the scope of producing Go code and tests.
Install Mechanism
There is no install spec and no code files to execute; the skill is instruction-only. This is the lowest-risk install model and consistent with the skill's purpose.
Credentials
The skill declares no required environment variables, credentials, or config paths. The guidance mentions common Go libraries (e.g., go-playground/validator) but does not request keys or secrets; this is proportionate to a coding-persona skill.
Persistence & Privilege
always is false and autonomous invocation is the platform default. The skill does not request elevated persistence or configuration changes to other skills or system-wide settings.
Assessment
This is an instruction-only, opinionated Go web-development persona that asks for no credentials and performs no I/O outside advising how to write code and tests. It appears coherent and low-risk. Before installing, consider whether its strict rules (zero global state, mandatory wrapping style, validator usage, test requirements) match your existing codebase and team conventions—it may require stylistic or architectural changes. If you plan to let agents invoke skills autonomously, remember the agent could produce or modify code using these conventions; audit generated code before deploying it in production.

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

latestvk9755bemzjd64cpbm2x1azf9k183d8vn

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments