use-modern-go

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

Quality

74%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./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 features by version with concrete before/after code examples. The dynamic version detection mechanism is clever and practical. The only weakness is that the extensive feature catalog could benefit from being split into a separate reference file to improve progressive disclosure, though the version-based section headers provide good internal navigation.

Suggestions

Consider extracting the detailed 'Features by Go Version' section into a separate REFERENCE.md file, keeping only a summary table or the most critical features (Go 1.24+) inline in SKILL.md.

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 section delivers concrete syntax patterns with minimal prose. The before/after examples are terse and purposeful.	3 / 3
Actionability	Every feature is accompanied by executable, copy-paste-ready Go code examples. The before/after patterns make it unambiguous what to use and what to avoid. The dynamic version detection via the shell command is a concrete, actionable mechanism.	3 / 3
Workflow Clarity	The workflow is clear and well-sequenced: detect version → communicate to user → apply features up to that version. The decision tree for detected vs unknown versions is explicit with specific dialogue templates. For a reference/guideline skill (not a destructive multi-step operation), this level of workflow clarity is appropriate and complete.	3 / 3
Progressive Disclosure	The content is well-organized with clear version-based sections and a logical hierarchy, but it's a single monolithic file with ~200 lines of feature reference that could benefit from being split (e.g., features by version in a separate reference file). There are no external file references or navigation aids for the detailed content.	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 'Use when' clause and is focused on Go, which helps with completeness and some distinctiveness. However, it is weak on specificity — it doesn't enumerate what 'modern Go syntax guidelines' actually include (e.g., generics, range-over-int, structured logging). Trigger terms are limited and miss common user phrasings.

Suggestions

Add specific concrete actions like 'Applies generics, range-over-int, structured logging, and other version-specific Go syntax patterns' to improve specificity.

Expand trigger terms in the 'Use when' clause to include natural variations like 'idiomatic Go', 'Go best practices', 'Go style guide', 'Go version features', or 'upgrading 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 does answer 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, even though both parts are somewhat thin.	3 / 3
Trigger Term Quality	Includes 'Go', 'Go code', 'modern', and 'guidelines' which are somewhat relevant, but misses natural 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 language which helps, but 'syntax guidelines' could overlap with general Go linting, Go style, or Go best practices skills. The 'based on project's Go version' adds some distinction but the scope is still somewhat ambiguous.	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: 16 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.