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
100%
Does it follow best practices?
Impact
87%
0.97xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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 (Go code style conventions), lists specific capabilities, provides explicit trigger conditions, and uniquely includes cross-references to related skills to minimize overlap. The explicit exclusions with pointers to sibling skills are a best practice that makes this description stand out for disambiguation in a multi-skill environment.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete aspects: 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 or reviewing Go code, asking about style or clarity, establishing project coding standards). Also explicitly states when NOT to use it 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'. The explicit exclusions with cross-references also help disambiguate trigger terms like 'naming conventions', 'linter', and 'doc comments'. | 3 / 3 |
Distinctiveness Conflict Risk | Exceptionally distinctive — not only defines its own clear niche (Go code style conventions) but explicitly delineates boundaries by listing related skills that handle naming, linting, and documentation. This dramatically reduces conflict risk with sibling skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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-organized. It provides clear, opinionated Go style guidance with executable code examples, appropriate use of MUST/SHOULD language, and well-signaled cross-references to related skills. The content respects Claude's intelligence while adding genuine value through specific, judgment-based style rules that linters can't enforce.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient throughout. It assumes Claude's Go competence, avoids explaining basic concepts, and every section delivers actionable rules with minimal preamble. Code examples are tight and illustrative without unnecessary commentary. | 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/conventions skill rather than a multi-step process skill. The single-task guidance is unambiguous, with clear MUST/SHOULD directives. The parallelizing code reviews section provides a clear workflow for the one multi-step scenario. No destructive or batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections, appropriate cross-references to related skills (naming, lint, design patterns, structs/interfaces), and references to a details.md file for deeper content. Navigation is one level deep and clearly signaled throughout. | 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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
- Commit
8c7e016
- 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.