Tessl • The management layer for AI agent skills

SkillPublic

golang-patterns

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

Quality

57%

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

Quality

Content

50%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 well-organized and highly actionable with executable Good/Bad code examples, but it largely restates standard Go knowledge Claude already has and crams everything into a single large file. It works as a generic Go cheatsheet rather than a skill that adds non-obvious, project-specific value.

Suggestions

Trim or remove sections covering textbook Go idioms (zero values, error wrapping, strings.Builder, sync.Pool) and keep only conventions Claude would not already apply by default.

Split the 675-line body into one-level-deep reference files (e.g. references/concurrency.md, references/tooling.md) with clearly signaled links from a concise SKILL.md overview.

Add a short sequenced workflow for the skill's activation cases (e.g. how to review or refactor existing Go code against these patterns, with a go vet/staticcheck validation checkpoint).

Dimension	Reasoning	Score
Conciseness	The ~675-line body catalogs standard Go idioms Claude already knows (zero values, "Accept Interfaces, Return Structs", error wrapping with %w, strings.Builder, sync.Pool, worker pools, gofmt) without adding project-specific knowledge. It avoids padded prose (above anchor 1) but the sheer volume of already-known material makes it noticeably verbose.	2 / 5
Actionability	Concrete, complete code examples with Good/Bad contrast (e.g. the LoadConfig error-wrapping function, GracefulShutdown, the functional-options pattern) plus real commands ("go test -race ./...", "golangci-lint run") and a copy-paste .golangci.yml. Minor gaps keep it below anchor 5: several snippets call undefined helpers like db.FindUser, process, and fetch.	4 / 5
Workflow Clarity	This is a reference catalog, not a multi-step process: there is a "When to Activate" section and well-organized topic sections, but no sequenced workflow, no validation checkpoints, and no guidance on how to apply the patterns during code review or refactoring. It is above anchor 2 because each section is unambiguous in itself, but the simple-skill exception does not apply to a 675-line skill.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent), so all content sits in one monolithic 675-line SKILL.md with good section headers and a quick-reference table. Material that clearly belongs in separate reference files (concurrency patterns, tooling/linter configuration) is inlined, which is better organized than anchor 2 but lacks the file split that anchor 4 would show.	3 / 5
	Total	12 / 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 scopes the skill to Go and is unlikely to collide with unrelated skills, but it describes topics rather than actions and entirely lacks a 'Use when...' activation clause. Adding concrete capabilities and trigger phrases would lift it substantially.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. "Use when writing, reviewing, or refactoring Go (golang) code, designing Go packages, or when the user asks about idiomatic Go."

Replace the abstract noun list with 2-3 concrete actions, e.g. "Applies idiomatic Go patterns for error handling, concurrency, and interface design; reviews and refactors Go code against Go conventions."

Drop the buzzword string "robust, efficient, and maintainable" in favor of specific capability or trigger language.

Dimension	Reasoning	Score
Specificity	The description is a noun list of topics ("Idiomatic Go patterns, best practices, and conventions") with no concrete actions, and "robust, efficient, and maintainable" reads as buzzword padding. It names the Go domain explicitly (above anchor 1) but never states what the skill actually does (below anchor 3).	2 / 5
Completeness	There is a moderately clear 'what' (a reference of Go patterns and conventions) but no 'when' guidance at all, which caps completeness at 3 per the judging guidelines. It does not fall to 2 because the 'what' is domain-specific and not entirely vague, and cannot reach 4 without any activation clause.	3 / 5
Trigger Term Quality	"Go" and "Idiomatic" are natural, relevant keywords a user would say, but common variations like "golang", "Go code", or "Go code review" are missing. This matches anchor 3: some relevant keywords, missing common variations or synonyms.	3 / 5
Distinctiveness Conflict Risk	"Idiomatic Go patterns... for building... Go applications" is clearly Go-scoped, giving it a distinct niche with minimal conflict risk against non-Go skills. It falls short of anchor 5 only because no explicit triggers are stated to sharpen distinctiveness further.	4 / 5
	Total	12 / 20 Passed

Validation

87%

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 — 14 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: valeriibeck-star/claude-skills
Path: skills/golang-patterns/SKILL.md
Revision: 0bda8b8

Reviewed: 2 days ago

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.

golang-patterns

Table of Contents

Is this your skill?