use-modern-go

Apply modern Go syntax guidelines based on project's Go version. Use when user ask for modern Go code guidelines.

2.20x

Quality

74%

Does it follow best practices?

Impact

86%

2.20x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./claude/modern-go-guidelines/skills/use-modern-go/SKILL.md

Quality

Content

92%

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

This is an excellent, highly actionable skill that efficiently catalogs modern Go idioms organized by version with concrete before/after code examples. The version detection mechanism via embedded shell command is clever and the behavioral instructions are precise. The only weakness is the length of the single file—the feature reference section is extensive and could benefit from being split into separate files by version range for better progressive disclosure.

Suggestions

Consider splitting the feature-by-version reference into a separate FEATURES.md or version-grouped files (e.g., GO_1_21_PLUS.md) and keeping SKILL.md as a concise overview with links, to improve progressive disclosure and reduce token cost when only a subset of versions is relevant.

Dimension	Reasoning	Score
Conciseness	The skill is highly token-efficient. It assumes Claude's Go competence, provides no unnecessary explanations of what Go is or how packages work, and every entry is a terse before/after pattern or one-liner showing the modern idiom. No filler text.	3 / 3
Actionability	Every feature includes concrete, copy-paste-ready code examples with clear before/after patterns. The instructions for version detection and user interaction are specific and executable, including the exact shell command for version detection and exact phrasing for responses.	3 / 3
Workflow Clarity	The workflow is clear and well-sequenced: detect version via embedded command, respond with specific phrasing based on result, then apply all features up to that version. For a reference/guideline skill (not a destructive multi-step operation), the workflow is unambiguous with clear decision points for known vs unknown versions.	3 / 3
Progressive Disclosure	The content is well-organized with clear version-based sections and a logical hierarchy, but it's a long monolithic document (~200 lines of feature listings). The version-specific feature blocks could potentially be split into separate files or collapsed, though for a standalone skill without bundle files this is a reasonable single-file approach.	2 / 3
	Total	11 / 12 Passed

Description

57%

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 provides a clear 'what' and 'when' structure but lacks specificity about what concrete actions or guidelines it covers. The trigger terms are limited and the capabilities described are too abstract to help Claude confidently distinguish this skill from other Go-related skills.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Applies generics syntax (Go 1.18+), structured logging with slog (Go 1.21+), range-over-func (Go 1.23+), and other version-specific features.'

Expand trigger terms in the 'Use when' clause to include natural variations like 'idiomatic Go', 'Go best practices', 'Go style guide', 'Go version features', 'update Go syntax'.

Dimension	Reasoning	Score
Specificity	The description says 'apply modern Go syntax guidelines' which is vague — it doesn't list any concrete actions like specific syntax features, patterns, or transformations. 'Modern Go syntax guidelines' is abstract without examples of what those guidelines entail.	1 / 3
Completeness	It answers both 'what' (apply modern Go syntax guidelines based on project's Go version) and 'when' (when user asks for modern Go code guidelines) with an explicit 'Use when' clause, though both parts are thin on detail.	3 / 3
Trigger Term Quality	It includes 'Go', 'Go code', 'modern', and 'guidelines' which are somewhat relevant, but misses common variations users might say like 'Go best practices', 'idiomatic Go', 'Go style', 'Go conventions', 'Go version compatibility', or specific version numbers.	2 / 3
Distinctiveness Conflict Risk	It's specific to Go syntax guidelines which narrows the domain, but could overlap with general Go coding skills, Go linting skills, or Go best practices skills since 'modern Go syntax guidelines' is broad enough to conflict.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: JetBrains/go-modern-guidelines
Commit: 3e97bab

Reviewed: about 1 month 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.