golang-patterns

Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.

Quality

68%

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 ./docs/zh-TW/skills/golang-patterns/SKILL.md

Quality

Content

72%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 content is highly actionable and concise, packed with executable Go examples, but it is a monolithic reference catalog with no progressive disclosure into bundle files and no sequenced workflow with validation checkpoints.

Suggestions

Split large reference blocks (the .golangci.yml config, project structure tree, and idiom quick-reference table) into separate files under references/ and link to them from SKILL.md to improve progressive disclosure.

If the skill is meant to guide a multi-step task, add an explicit sequenced workflow with validation checkpoints; otherwise clarify it is a pure reference catalog so workflow expectations are calibrated.

Trim a few redundant explanatory code comments to push conciseness toward a lean 5.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable code and minimal prose, assuming Claude's Go competence; one-line section intros and no padding about what Go is, with only minor trimmable comment lines.	4 / 5
Actionability	Provides fully executable, copy-paste-ready Go examples covering the common cases (error wrapping, worker pools, context, errgroup, functional options, sync.Pool) with concrete good/bad contrasts.	5 / 5
Workflow Clarity	This is a pattern catalog rather than a sequenced process; sections provide rough organization but there are no explicit validation checkpoints or feedback loops, and the 'when to enable' triggers are not a workflow.	3 / 5
Progressive Disclosure	All content (~670 lines) is inlined in a single SKILL.md with no bundle files or external references; section headers give some structure, but content that could be split (linter config, project layout, idiom table) is inlined rather than offloaded.	3 / 5
	Total	15 / 20 Passed

Description

65%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 a distinct Go niche and uses natural trigger terms, but it lacks an explicit 'when to use' clause and frames capabilities as abstract topics rather than concrete actions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when writing, reviewing, refactoring, or designing Go packages and modules.'

Replace abstract qualities with concrete actions, e.g. 'Apply idiomatic error handling, concurrency, and interface patterns' instead of 'robust, efficient, and maintainable'.

Include common synonyms/extensions like 'golang' and '.go files' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Go domain and lists content categories ('patterns, best practices, conventions') plus target qualities ('robust, efficient, and maintainable'), but these are abstract topics rather than concrete executable actions, fitting the 'names domain and 1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Provides a clear 'what' (idiomatic Go patterns and conventions) but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Idiomatic Go', 'best practices', 'conventions') with good coverage, but misses common synonyms and extensions like 'golang' or '.go'.	4 / 5
Distinctiveness Conflict Risk	'Idiomatic Go patterns' is a clear, narrow niche with distinct triggers and minimal risk of firing for unrelated skills.	5 / 5
	Total	15 / 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
skill_md_line_count	SKILL.md is long (675 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: docs/zh-TW/skills/golang-patterns/SKILL.md
Commit: d8409a4

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