go-best-practices
Provides Go patterns for type-first development with custom types, interfaces, functional options, and error handling. Must use when reading or writing Go files.
83
Quality
76%
Does it follow best practices?
Impact
91%
1.10xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xbigboss/claude-code/go-best-practices/SKILL.mdQuality
Discovery
75%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 description has strong completeness with an explicit 'Must use when' clause and clear scope to Go files. However, it could be more specific about concrete actions (what Claude will actually do with these patterns) and include more natural trigger terms like 'golang' or '.go' that users commonly use.
Suggestions
Add concrete actions like 'Generates custom types', 'Implements interfaces', 'Applies functional options pattern' instead of just listing concepts
Expand trigger terms to include common variations: 'golang', '.go files', 'Go code', 'Go programming'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Go) and lists several concepts (custom types, interfaces, functional options, error handling), but these are patterns/concepts rather than concrete actions like 'create', 'validate', or 'refactor'. | 2 / 3 |
Completeness | Clearly answers both what ('Provides Go patterns for type-first development with custom types, interfaces, functional options, and error handling') and when ('Must use when reading or writing Go files') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Go files' which users would naturally mention, but misses common variations like '.go', 'golang', 'Go code', or specific pattern names users might search for. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Go language with specific focus on type-first development patterns; unlikely to conflict with other language skills or general coding skills due to explicit Go file trigger. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid Go best practices skill with excellent actionability - all code examples are executable and demonstrate real patterns. The type-first workflow is clearly articulated. Main weaknesses are minor verbosity in explanatory comments that Claude doesn't need, and the content could be better organized with progressive disclosure to separate reference material from core patterns.
Suggestions
Remove explanatory comments that state the obvious (e.g., '// Compiler prevents passing OrderID here', 'Panics crash the program') - Claude knows these implications
Consider splitting detailed examples (Configuration section, full enum implementation) into a separate EXAMPLES.md or PATTERNS.md file, keeping SKILL.md as a concise overview
Remove the rationale sentences after each instruction bullet (e.g., 'This preserves the error chain for debugging') - the instruction itself is sufficient
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some explanatory comments that Claude already knows (e.g., 'Compiler prevents passing OrderID here', 'Panics crash the program'). The rationale comments after instructions add tokens without adding value for Claude. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all snippets are copy-paste ready with proper imports shown, concrete patterns for custom types, functional options, error handling, and configuration. No pseudocode; everything is directly usable. | 3 / 3 |
Workflow Clarity | Clear 4-step type-first development workflow at the top. For a patterns/best-practices skill (not a multi-step destructive operation), the structure is appropriate. Each section has clear purpose and the instructions section provides explicit guidance. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic file (~200 lines) that could benefit from splitting detailed examples (config, functional options) into separate reference files. No external file references for advanced topics. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
5342bca
- 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.