tessl-labs/go-project-structure
Go project structure -- cmd/internal layout, handler/service/repository layers, Makefile, config from environment, domain error types, test placement, dependency injection
90
84%
Does it follow best practices?
Impact
100%
1.02xAverage score across 5 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 hits all the marks. It provides comprehensive specificity about Go project structure conventions, includes natural trigger terms developers would actually use, explicitly states both what it does and when to use it, and carves out a clear niche that distinguishes it from generic coding or project setup skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: cmd/internal/pkg layout, handler/service/repository layers, Makefile with standard targets, go.mod management, configuration from environment, test file placement, dependency injection, and domain error types. | 3 / 3 |
Completeness | Clearly answers both what (Go project structure with specific patterns and conventions) AND when with explicit 'Use when...' clause and detailed 'Triggers on:' list covering multiple scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'new Go microservice', 'Go API project setup', 'set up a Go project', 'monolithic main.go', 'Go project scaffolding', 'handler separation', 'Go configuration management' - these match how developers naturally describe their needs. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically Go web APIs/microservices with particular architectural patterns (cmd/internal/pkg, handler/service/repository). Unlikely to conflict with general Go skills or other language project setup skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a thorough, highly actionable Go project structure guide with excellent executable code examples covering all major patterns. The main weaknesses are verbosity (explaining concepts Claude knows, like Go's internal/ enforcement) and lack of explicit workflow sequencing for project setup. The content would benefit from being split into a concise overview with links to detailed pattern files.
Suggestions
Add a step-by-step 'New Project Setup' workflow at the top with explicit verification steps (e.g., '1. Create directory structure, 2. Run go mod init, 3. Verify with go build ./...')
Move detailed code examples (full main.go, complete handler implementations) to separate reference files and link from SKILL.md
Remove explanations of Go compiler behavior Claude already knows (e.g., the 'Why internal/ matters' section explaining import blocking)
Add a 'Verify your setup' section with commands to validate the project structure is correct before proceeding
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant explanations (e.g., explaining why internal/ matters when Claude knows Go's import rules). The content is well-organized but could be tightened—some sections repeat concepts and the overall length (~600 lines) is substantial for patterns Claude likely knows. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready code examples throughout. Every pattern includes complete, working Go code with proper imports, struct definitions, and function implementations. The Makefile, .gitignore, and all code snippets are immediately usable. | 3 / 3 |
Workflow Clarity | The skill presents clear patterns but lacks explicit validation checkpoints or feedback loops. The 'Quick Checklist' at the end is helpful, but there's no step-by-step workflow for setting up a new project with verification steps between stages. The 'When NOT to Split' section provides good decision guidance but the main content reads more as reference than workflow. | 2 / 3 |
Progressive Disclosure | The skill references verifiers at the end but keeps all content inline in one large file. The content could benefit from splitting detailed code examples (like the full main.go with graceful shutdown) into separate reference files, with SKILL.md providing a concise overview and links to detailed implementations. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (827 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
Reviewed
Table of Contents