golang-lint
Provides linting best practices and golangci-lint configuration for Go projects. Covers running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and managing linter settings. Use this skill whenever the user runs linters, configures golangci-lint, asks about lint warnings or suppressions, sets up code quality tooling, or asks which linters to enable for a Go project. Also use when the user mentions golangci-lint, go vet, staticcheck, revive, or any Go linting tool.
97
100%
Does it follow best practices?
Impact
96%
1.31xAverage 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, lists concrete capabilities, and provides comprehensive trigger guidance. It names specific tools and file types that make it highly distinguishable, and the explicit 'Use this skill whenever...' clause covers a thorough range of user scenarios. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and managing linter settings. These are clearly defined, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (linting best practices, configuration, running linters, suppressing warnings, interpreting output) and 'when' with an explicit 'Use this skill whenever...' clause listing multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'golangci-lint', 'go vet', 'staticcheck', 'revive', 'lint warnings', 'nolint', '.golangci.yml', 'code quality tooling', 'linters'. These are the exact terms a Go developer would use when seeking linting help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Go-specific linting with named tools (golangci-lint, go vet, staticcheck, revive) and specific artifacts (.golangci.yml, nolint directives). Unlikely to conflict with general Go development or other language linting 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 a high-quality skill that excels across all dimensions. It provides a concise yet comprehensive overview of Go linting with golangci-lint, featuring executable commands, clear workflows with multiple entry points (setup/coding/fix modes), and excellent progressive disclosure to reference materials. The content respects Claude's intelligence while adding genuine value through specific configuration guidance, troubleshooting tables, and parallelization strategies.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what linting is or how Go works, assumes Claude's competence, and every section delivers actionable information without padding. The persona/modes section at the top is slightly verbose but provides genuinely useful behavioral guidance. | 3 / 3 |
Actionability | Provides fully executable bash commands, concrete Go code examples for nolint directives, copy-paste ready Makefile targets, and a specific troubleshooting table with exact solutions. The quick reference section alone gives Claude everything needed to run linters immediately. | 3 / 3 |
Workflow Clarity | The development workflow is clearly sequenced (run → fix → format → commit), the modes at the top define clear entry points for different scenarios, and the interpreting output section provides a feedback loop (identify linter → look up reference → fix or suppress). The legacy cleanup parallelization strategy adds structured guidance for complex operations. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure: the SKILL.md serves as a concise overview with well-signaled one-level-deep references to ./assets/.golangci.yml, ./references/linter-reference.md, ./references/nolint-directives.md, and cross-references to related skills. Content is appropriately split between overview and detailed reference materials. | 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
26524a3
- 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.