Content
63%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-organized, highly concrete catalog of idiomatic Go patterns with consistent good/bad code comparisons and ready-to-use tooling configuration. Its main weaknesses are that a meaningful portion restates basic Go knowledge Claude already has, and everything is packed into one long file with no progressive disclosure via reference files. Trimming the Go-101 material and splitting the linter config and specialized pattern sections into references would raise both conciseness and structure scores.
Suggestions
Cut or compress sections that restate Go fundamentals Claude already knows (zero values, single-method interfaces, strings.Join vs concatenation) and keep only the non-obvious or project-specific conventions.
Move the .golangci.yml configuration and the performance/antipattern catalogs into a references/ file (e.g., references/linting.md, references/antipatterns.md) linked from the body, so SKILL.md stays a lean overview.
Differentiate guidance for the four stated use cases (writing new code, reviewing, refactoring, package design) — e.g., a short per-scenario checklist — so the 'when to activate' section translates into distinct actions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is reference-style with lean good/bad code pairs and almost no padded prose, but a substantial share restates Go fundamentals Claude already knows (zero values, small single-method interfaces, prefer strings.Join over concatenation, run gofmt). Fits 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not 2 because there is no prose padding, and not 4 because several sections teach basic Go 101 that could be cut. | 3 / 5 |
Actionability | Nearly every section gives concrete, compilable-pattern code (error wrapping with %w, errors.Is/As, errgroup, functional options, graceful shutdown) plus copy-paste-ready tooling (go test -race commands, a full .golangci.yml). Fits 'Mostly executable guidance; concrete code or commands with minor gaps'; not 5 because several snippets depend on undefined helpers (db.FindUser, process(job), fetch) so they are not fully copy-paste runnable. | 4 / 5 |
Workflow Clarity | This is a reference skill with no multi-step or destructive workflow, so no validation checkpoints are required; the '何時啟用' section signals when to apply the material and the organization (principles → error handling → concurrency → interfaces → layout → performance → antipatterns) is coherent. Fits 'Clear sequence with most checkpoints present' in the sense of unambiguous application guidance; not 5 because the four stated use cases (writing, reviewing, refactoring, designing) are not differentiated with scenario-specific guidance. | 4 / 5 |
Progressive Disclosure | The single SKILL.md is well-organized with clear headers, but there are no bundle files at all — everything is inlined in one ~670-line file, and self-contained chunks like the .golangci.yml linter configuration, performance patterns, and antipattern catalog are natural candidates for separate reference files. Fits 'Some structure but could be better organized; content that should be separate is inline'; not 4 because no references exist and the file far exceeds the under-50-line simple-skill case. | 3 / 5 |
Total | 14 / 20 Passed |