golang-project-layout

Provides a guide for setting up Golang project layouts and workspaces. Use when starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, deciding between cmd/internal/pkg directory conventions, or discussing package restructuring, package splits, or module splits.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

78%Weight 40%Scale 1-5

Reviews 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-structured, lean overview that pushes detail into real reference files and sibling skills, with concrete commands and a sequenced initialization checklist. It is held just below top marks on conciseness/actionability/workflow by minor padding and the lack of an explicit validation feedback loop.

Suggestions

Add an explicit validation checkpoint to the initialization checklist (e.g., run 'go build ./...' or 'golangci-lint run' after gofmt, with a fix-and-retry step) to lift workflow clarity.

Tighten the '12-Factor App' section to a single pointer line rather than restating the factors Claude already knows.

Inline one concrete 'go work init ./module-a ./module-b' example in the Workspaces section so the core action is executable without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is efficient and mostly assumes Claude's competence — it delegates detail to references and sibling skills rather than re-explaining Go basics; minor trimmable spots exist (e.g., the brief 12-Factor restatement), keeping it just below a 5.	4 / 5
Actionability	Provides concrete, executable commands and examples ('go mod init github.com/user/project-name', 'gofmt -s -w .', good/bad module-path code blocks, the cmd/{name}/main.go pattern) with only minor gaps where guidance defers entirely to referenced skills (DI, linting).	4 / 5
Workflow Clarity	The 'Initialization Checklist' plus the 'Ask First'/'Ask Next' decision sequence give a clear ordered process with implicit checkpoints (go version detection, gofmt formatting); not a 5 because there is no explicit validate→fix→retry feedback loop, though the setup task is not inherently destructive.	4 / 5
Progressive Disclosure	Clear overview with well-signaled, one-level-deep references to real bundle files (references/directory-layouts.md, references/config.md, references/testing-layout.md, references/workspaces.md, assets/Makefile, assets/.gitignore) plus clearly labeled cross-links to sibling skills; navigation is easy and content is appropriately split.	5 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states a clear purpose, uses third person, and pairs a concrete 'what' with an explicit, multi-trigger 'when' clause. Trigger and distinctiveness are excellent; specificity is slightly held back only by the generic 'Provides a guide' framing.

Dimension	Reasoning	Score
Specificity	Enumerates several concrete scenarios — 'setting up Golang project layouts and workspaces', 'setting up a monorepo with multiple packages', 'creating CLI tools with multiple main packages', 'deciding between cmd/internal/pkg directory conventions', 'package restructuring, package splits, or module splits' — with only minor gaps in coverage; not a full 5 because the core verb is the generic 'Provides a guide'.	4 / 5
Completeness	Explicitly answers both what ('Provides a guide for setting up Golang project layouts and workspaces') and when ('Use when starting a new Go project...'), with a concrete multi-clause trigger list; uses third person ('Provides'), so no voice penalty.	5 / 5
Trigger Term Quality	Strong natural-term coverage including synonyms and variants ('new Go project', 'monorepo', 'CLI tools', 'cmd/internal/pkg', 'package splits', 'module splits', 'package restructuring'); falls just short of 5 because it omits a few common phrasings like 'go.mod' or 'Go modules'.	4 / 5
Distinctiveness Conflict Risk	Clear niche — Go-specific layout/workspace guidance with distinct directory-convention and module-split triggers — that is unlikely to fire for non-Go skills, giving minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: samber/cc-skills-golang
Path: skills/golang-project-layout/SKILL.md
Commit: 30cdf15

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.