CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

golang-patterns

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

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 a well-organized, highly concrete catalog of idiomatic Go patterns with consistent good/bad code comparisons and ready-to-use tooling configuration. Its main weaknesses are that a meaningful portion restates basic Go knowledge Claude already has, and everything is packed into one long file with no progressive disclosure via reference files. Trimming the Go-101 material and splitting the linter config and specialized pattern sections into references would raise both conciseness and structure scores.

Suggestions

Cut or compress sections that restate Go fundamentals Claude already knows (zero values, single-method interfaces, strings.Join vs concatenation) and keep only the non-obvious or project-specific conventions.

Move the .golangci.yml configuration and the performance/antipattern catalogs into a references/ file (e.g., references/linting.md, references/antipatterns.md) linked from the body, so SKILL.md stays a lean overview.

Differentiate guidance for the four stated use cases (writing new code, reviewing, refactoring, package design) — e.g., a short per-scenario checklist — so the 'when to activate' section translates into distinct actions.

DimensionReasoningScore

Conciseness

The body is reference-style with lean good/bad code pairs and almost no padded prose, but a substantial share restates Go fundamentals Claude already knows (zero values, small single-method interfaces, prefer strings.Join over concatenation, run gofmt). Fits 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not 2 because there is no prose padding, and not 4 because several sections teach basic Go 101 that could be cut.

3 / 5

Actionability

Nearly every section gives concrete, compilable-pattern code (error wrapping with %w, errors.Is/As, errgroup, functional options, graceful shutdown) plus copy-paste-ready tooling (go test -race commands, a full .golangci.yml). Fits 'Mostly executable guidance; concrete code or commands with minor gaps'; not 5 because several snippets depend on undefined helpers (db.FindUser, process(job), fetch) so they are not fully copy-paste runnable.

4 / 5

Workflow Clarity

This is a reference skill with no multi-step or destructive workflow, so no validation checkpoints are required; the '何時啟用' section signals when to apply the material and the organization (principles → error handling → concurrency → interfaces → layout → performance → antipatterns) is coherent. Fits 'Clear sequence with most checkpoints present' in the sense of unambiguous application guidance; not 5 because the four stated use cases (writing, reviewing, refactoring, designing) are not differentiated with scenario-specific guidance.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized with clear headers, but there are no bundle files at all — everything is inlined in one ~670-line file, and self-contained chunks like the .golangci.yml linter configuration, performance patterns, and antipattern catalog are natural candidates for separate reference files. Fits 'Some structure but could be better organized; content that should be separate is inline'; not 4 because no references exist and the file far exceeds the under-50-line simple-skill case.

3 / 5

Total

14

/

20

Passed

Description

48%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 is unlikely to trigger for unrelated skills, but it reads as a topic list rather than a capability statement and contains no 'use when' trigger guidance. Users asking to 'review my golang code' or 'refactor this .go file' would not be reliably routed to it. Adding an explicit trigger clause and one or two concrete actions would substantially improve it.

Suggestions

Add an explicit trigger clause, e.g., 'Use when writing, reviewing, refactoring, or designing Go code, or when the user mentions Go, golang, or .go files.'

Replace the topic list with concrete capability actions, e.g., 'Apply idiomatic Go patterns for error handling, concurrency, interface design, and package layout when writing or reviewing Go code.'

Include the common synonyms users actually say — 'golang' and '.go files' — to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Idiomatic Go patterns, best practices, and conventions') but lists topics rather than concrete actions — there is no verb describing what the skill actually does (e.g., write, review, refactor). This matches the anchor 'Names the domain but actions are minimal or generic'; it is not a 3 because no specific capability actions are stated.

2 / 5

Completeness

There is a moderately clear 'what' (a reference of idiomatic Go patterns and conventions) but no 'when' — no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant keywords like 'Go', 'idiomatic', and 'best practices' are present, but common natural variations users would say are missing: 'golang', '.go files', 'refactor', 'goroutine/concurrency'. Fits 'Some relevant keywords but missing common variations or synonyms'; not 4 because several natural trigger phrases are absent.

3 / 5

Distinctiveness Conflict Risk

The description is explicitly scoped to 'Go' and 'Go applications', making it clearly distinguishable from skills for other languages or file formats, with only minor overlap risk against a hypothetical Go-tooling or general code-review skill. Fits 'Mostly distinct; minor overlap risk with closely related skills'; not 5 because it lacks distinct concrete trigger phrases that would fully separate it.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.