golang-patterns

Patrones idiomáticos de Go, buenas prácticas y convenciones para construir aplicaciones Go robustas, eficientes y mantenibles.

Quality

53%

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

Quality

Content

57%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, largely executable catalog of idiomatic Go patterns with strong code examples, but it is over-long for SKILL.md (re-teaching well-known Go idioms) and inlines reference material that belongs in separate bundled files. Splitting detailed references out and trimming familiar content would improve both conciseness and progressive disclosure.

Suggestions

Move the linter configuration, project-layout reference, and anti-pattern catalog into separate files under references/ and link to them one level deep, keeping SKILL.md as an overview.

Trim sections that restate well-known Go idioms (sync.Pool, strings.Builder, embedding) to focus the body on non-obvious or project-specific guidance.

Add a brief "Cómo usar esta skill" workflow step (e.g. identify pattern area → apply pattern → run `go vet`/`go test -race` to validate) to give the reference a light validation checkpoint.

Dimension	Reasoning	Score
Conciseness	Per-section content is lean (mostly labeled Bien/Mal code with little prose), but the ~670-line body re-teaches idiomatic Go that Claude already knows (sync.Pool, errgroup, embedding, functional options), so it could be tightened considerably to assume Claude's competence — the 3 anchor (mostly efficient but includes unnecessary material) fits better than the lean 4.	3 / 5
Actionability	It provides mostly executable, copy-paste-ready patterns across many common cases (error wrapping, worker pools, graceful shutdown, functional options) plus runnable tooling commands, but several examples rely on undefined helper placeholders (process, fetch, db.FindUser), leaving minor gaps that keep it just below a 5.	4 / 5
Workflow Clarity	This is a reference catalog of patterns, not a sequenced multi-step process: it is well organized by topic with a clear "Cuándo Activar" section, but there is no workflow sequence or validation checkpoints to evaluate, so it sits at the "steps/checkpoints implicit or absent" level rather than a 4.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and all content — including bulk reference material like the linter config, project layout, and anti-pattern catalog — is inlined in one ~670-line SKILL.md; the section structure is good, but at this size a skill should split detailed reference material into separate one-level-deep files with clear links, matching the 3 anchor.	3 / 5
	Total	13 / 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 niche and what it covers, but stops short of listing concrete actions or any explicit "Use when" trigger guidance. Adding specific capabilities and a usage-trigger clause would lift the completeness and specificity scores.

Suggestions

Add 1-2 concrete capabilities, e.g. "documenta manejo de errores, concurrencia y diseño de interfaces" instead of generic "buenas prácticas y convenciones".

Append an explicit "Úsar cuando se escriba, revise o refactorice código Go" clause to provide clear activation triggers.

Include the common synonym "golang" alongside "Go" so the description matches natural user phrasing.

Dimension	Reasoning	Score
Specificity	The description names the Go domain but its actions are generic and abstract — "patrones idiomáticos", "buenas prácticas", "convenciones", "construir aplicaciones" — without listing concrete capabilities, matching the "names domain but actions minimal/generic" anchor rather than the 1-2 concrete actions needed for a 3.	2 / 5
Completeness	It gives a clear "what" (idiomatic Go patterns and best practices for building Go applications) but includes no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	It surfaces relevant natural terms ("Go", "patrones", "buenas prácticas", "convenciones") a user might say, but misses common variations and synonyms like "golang" or "Go code review", fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The Go-specific niche ("patrones idiomáticos de Go") is mostly distinct with only minor overlap risk against generic code-review or best-practices skills, matching the "mostly distinct; minor overlap risk" anchor rather than the clearly-bounded niche of a 5.	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: affaan-m/ECC
Path: docs/es/skills/golang-patterns/SKILL.md
Commit: c70874f

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.