CtrlK
BlogDocsLog inGet started
Tessl Logo

golang-code-style

Golang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt. Use when writing or reviewing Go code, asking about style or clarity, or establishing project coding standards. Not for naming conventions (→ See `samber/cc-skills-golang@golang-naming` skill), linter configuration (→ See `samber/cc-skills-golang@golang-lint` skill), or doc comments (→ See `samber/cc-skills-golang@golang-documentation` skill).

95

0.97x
Quality

100%

Does it follow best practices?

Impact

87%

0.97x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 skill file that is concise, highly actionable, and well-structured. It provides clear, executable Go code examples for every style rule, assumes Claude's competence with Go fundamentals, and uses progressive disclosure effectively through cross-references to related skills and a details file. The only minor note is that the referenced `./references/details.md` file is not provided in the bundle, but the skill content stands well on its own.

DimensionReasoningScore

Conciseness

The skill is lean and efficient throughout. It assumes Claude knows Go fundamentals and never explains basic concepts. Every section provides actionable rules with minimal preamble, and code examples are tight and purposeful.

3 / 3

Actionability

Nearly every rule is accompanied by executable, copy-paste-ready Go code examples showing both good and bad patterns. Concrete guidance is given for line breaking, variable declarations, control flow, function design, and more — all with specific, real-world Go idioms.

3 / 3

Workflow Clarity

This is primarily a style/convention skill rather than a multi-step process skill. The single-task nature (applying style rules when writing/reviewing Go code) is unambiguous. The parallelizing code reviews section provides a clear workflow for batch review. The 'when ignoring a rule, add a comment' instruction provides a lightweight validation checkpoint.

3 / 3

Progressive Disclosure

The skill is well-organized with clear sections and cross-references to related skills (naming, lint, design patterns, structs/interfaces, CI). It references a details file for complex conditions and value vs pointer arguments. The content is appropriately scoped — not monolithic, not over-split.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that clearly defines its scope within a family of related Go skills. It provides specific capabilities, natural trigger terms, explicit 'use when' guidance, and uniquely includes 'not for' clauses with cross-references to sibling skills, making it highly distinguishable and easy for Claude to select correctly.

DimensionReasoningScore

Specificity

Lists multiple specific concrete areas: line length and breaking, variable declarations, control flow clarity, and when comments help vs hurt. These are concrete, actionable style topics rather than vague abstractions.

3 / 3

Completeness

Clearly answers both 'what' (Golang code style conventions covering line length, variable declarations, control flow, comments) and 'when' (writing/reviewing Go code, asking about style/clarity, establishing project coding standards). Also includes explicit 'not for' guidance with cross-references.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'Go code', 'Golang', 'style', 'clarity', 'coding standards', 'writing or reviewing Go code'. Also includes negative triggers pointing to related skills, which helps with disambiguation.

3 / 3

Distinctiveness Conflict Risk

Exceptionally distinctive — explicitly carves out its niche by listing what it covers AND what it doesn't cover, with direct cross-references to sibling skills for naming, linting, and documentation. This makes conflict with related Go skills very unlikely.

3 / 3

Total

12

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

9

/

11

Passed

Repository
samber/cc-skills-golang
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.