golang-pro

Master Go 1.21+ with modern patterns, advanced concurrency, performance optimization, and production-ready microservices.

Quality

44%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/golang-pro/SKILL.md

The canonical home for this skill is golang-pro in rmyndharis/antigravity-skills

Quality

Content

35%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an expansive capability catalog restating widely-known Go knowledge with no executable examples or validation checkpoints. It needs concrete code, a verified workflow, and offloaded reference material to become actionable and token-efficient.

Suggestions

Cut the Capability and Knowledge Base bullet lists down to non-obvious expertise, and move exhaustive library/tool enumerations into a separate references file.

Add copy-paste-ready code examples for the highest-value tasks (worker pool with graceful shutdown, pprof profiling, context-based cancellation).

Turn the Instructions list into a real workflow with explicit validation checkpoints (e.g. run tests, check `go vet`/race detector, verify benchmarks) before proceeding.

Dimension	Reasoning	Score
Conciseness	The body is a long enumeration of capabilities Claude already knows (goroutine lifecycle, channel patterns, mutexes, GORM, golangci-lint, etc.) with no added insight, fitting anchor 2's "noticeably verbose; several unnecessary explanations or padded sections"; it is not 3 because almost nothing here is non-obvious expertise that earns its tokens.	2 / 5
Actionability	Guidance is high-level ("Choose concurrency and architecture patterns", "Implement with testing and profiling") with no executable code, commands, or concrete examples, matching anchor 2's minimal concrete guidance; it escapes 1 only because specific tool names (pprof, golangci-lint, slog, wire) are named.	2 / 5
Workflow Clarity	The Instructions section lists a real four-step sequence (confirm version, choose patterns, implement with testing/profiling, optimize) but has no validation checkpoints or feedback loops, matching anchor 3; it is not 4 because none of the steps include verification gates.	3 / 5
Progressive Disclosure	Section headers provide some structure, but large capability lists that belong in separate reference files are inlined and no bundle files exist, fitting anchor 3's "some structure but content that should be separate is inline"; it is not 4 because nothing is split out and navigation to deeper material is absent.	3 / 5
	Total	10 / 20 Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly identifies the Go domain and several capability areas but relies on the vague verb "Master" and omits any "Use when..." trigger guidance. Adding concrete actions and explicit trigger phrases would lift specificity and completeness.

Suggestions

Replace the generic verb "Master" with concrete actions, e.g. "Design, implement, profile, and optimize Go 1.21+ services and concurrency patterns."

Add an explicit trigger clause: "Use when building Go services, CLIs, or microservices, or when the user mentions Go, goroutines, channels, or Go profiling."

Include natural synonyms users say (goroutines, worker pools, pprof, go modules) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Go domain and several focus areas ("modern patterns, advanced concurrency, performance optimization, and production-ready microservices"), but the only action verb is the generic "Master" and the listed items are topics rather than concrete actions, so it sits at anchor 3 and not 4 (which requires several specific actions).	3 / 5
Completeness	It clearly states the "what" (master Go 1.21+ across the listed areas) but provides no "Use when..." trigger guidance, so per the boundary rule a missing trigger clause caps completeness at 3; it is not 2 because the "what" is explicit, and not 4 because the "when" is absent rather than weakly present.	3 / 5
Trigger Term Quality	Relevant keywords like "Go", "concurrency", "microservices", and "performance optimization" are present, but common natural phrasings and synonyms a user would actually say (e.g. "write a Go service", "optimize my Go code", "goroutines") are missing, matching anchor 3 rather than the more complete coverage of 4.	3 / 5
Distinctiveness Conflict Risk	The Go-specific framing ("Go 1.21+", concurrency, microservices) gives it a clear niche with only minor overlap risk against general programming skills, fitting anchor 4; it is not 5 because the lack of explicit trigger phrases leaves some ambiguity about when it should activate over adjacent skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/golang-pro/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.