Name: golang-code-style
Rating: 88.6 (1 reviews)
Author: samber

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).

0.98x

Quality

94%

Does it follow best practices?

Impact

67%

0.98x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

96%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.

An efficient, highly actionable style guide that pairs every rule with executable Go examples and offloads the two heaviest topics to a real reference file. Progressive disclosure is solid but could split more detail out of the main body.

Suggestions

Move the 'Code Organization Within Files' and 'Function Design' detail into references to further slim the main body and deepen progressive disclosure.

Add a brief validation checkpoint to the 'Parallelizing Code Style Reviews' workflow (e.g., dedup findings across sub-agents before reporting) to strengthen workflow_clarity for batch reviews.

Consolidate the repeated sibling-skill cross-references (currently scattered inline and again under 'Cross-References') into a single navigation block to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	Lean and dense, assuming Claude's Go competence — no padding explaining what slices or pointers are; every section delivers a rule with a tight good/bad example.	5 / 5
Actionability	Nearly every rule is paired with executable, copy-paste-ready Go code in good/bad form, covering the common cases concretely.	5 / 5
Workflow Clarity	As a single-purpose style reference the simple-skill exception applies: rules are unambiguous and grouped by concern, with a concrete parallelization workflow for codebase-scale reviews.	5 / 5
Progressive Disclosure	Good structure with well-signaled one-level-deep references to ./references/details.md (verified real) and cross-links to sibling skills, though reference usage is limited to two topics with most content inline.	4 / 5
	Total	19 / 20 Passed

Description

92%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.

A precise, well-scoped description that clearly states capabilities, trigger phrases, and boundaries against sibling skills. Only minor trigger-synonym coverage keeps it from a perfect sweep.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'line length and breaking, variable declarations, control flow clarity, when comments help vs hurt' — giving comprehensive coverage of the style domain.	5 / 5
Completeness	Explicitly answers both 'what' (the convention areas) and 'when' ('Use when writing or reviewing Go code...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural triggers ('writing or reviewing Go code, asking about style or clarity, establishing project coding standards') with good keyword coverage, though a few natural synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche with explicit 'Not for...' boundary clauses and cross-references to sibling naming, lint, and documentation skills, minimizing conflict risk.	5 / 5
	Total	19 / 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
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: samber/cc-skills-golang
Path: skills/golang-code-style/SKILL.md
Commit: 30cdf15

Reviewed: 5 days 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.