Name: golang-how-to
Rating: 69.6 (1 reviews)
Author: samber

golang-how-to

Golang skills orchestrator — always active on any Golang coding, review, debug, or setup task. Reads the task context and loads the most relevant skills from samber/cc-skills-golang, often multiple at once: writing a gRPC service loads golang-grpc + golang-testing + golang-error-handling; debugging a panic loads golang-troubleshooting + golang-safety; auditing security loads golang-security + golang-lint + golang-safety. Also: disambiguates competing clusters when two skills seem to overlap (performance vs benchmark vs troubleshooting, samber/lo vs mo vs ro, DI cluster, safety vs security), and configures the project's agent-config file (CLAUDE.md, AGENTS.md, GEMINI.md, Cursor rules, or Copilot instructions) to force-trigger skills in a project (/golang-how-to configure).

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

A well-structured orchestrator body that routes effectively via tables and concrete commands while pushing detail into clearly signaled one-level-deep references. The main weaknesses are mild repetition across the gopls/godig sections and implicit validation in the configure-mode file-writing workflow.

Suggestions

Consolidate the gopls/godig boundary explanation into one place; the 'Code navigation with gopls', the godig comparison table, and the 'Package lookup' cluster partially restate the same gopls-vs-godig division.

Add an explicit validation/verification checkpoint to the Configure-mode workflow in the body (e.g. confirm the directive landed in the correct agent-config file and is syntactically valid) rather than relying entirely on project-config.md.

Tighten the godig-vs-gopls-vs-Context7-vs-govulncheck table by moving per-task 'How' command detail into the referenced golang-pkg-go-dev / golang-security skills, keeping only the boundary decision in the body.

Dimension	Reasoning	Score
Conciseness	Mostly efficient tables and pointers that assume Go competence, but there is noticeable repetition (gopls described across several sections; the package-lookup cluster re-states the godig/gopls boundary) and the godig-vs-gopls comparison table is verbose enough to trim.	4 / 5
Actionability	Concrete routing tables (Intent → Primary → Also load) and copy-paste commands ("go install golang.org/x/tools/gopls@latest", "govulncheck ./...", "godig versions <path>") give mostly executable guidance; the bulk of execution is delegated to leaf skills, which is appropriate but leaves minor gaps inline.	4 / 5
Workflow Clarity	Three modes are clearly defined and the orchestrate workflow is a clear single action (load primary + secondary together at the start); configure mode has a user-confirmation loop and delegates detailed steps to project-config.md, leaving the file-write validation implicit in the body.	4 / 5
Progressive Disclosure	Clear overview body with three real, well-signaled one-level-deep references (by-category.md, disambiguation.md, project-config.md), with deep boundary tables and the full catalog appropriately split out for easy navigation.	5 / 5
	Total	17 / 20 Passed

Description

92%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.

A strong, concrete description that clearly states what the orchestrator does, when it activates, and how it differs from the leaf skills it routes to. The only gap is modest synonym/extension coverage in its trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "loads the most relevant skills", "disambiguates competing clusters", "configures the project's agent-config file" — each illustrated with specific multi-skill examples (gRPC loads grpc+testing+error-handling), giving comprehensive coverage of the orchestrator's scope.	5 / 5
Completeness	Explicitly answers both what (orchestrator that loads/disambiguates/configures skills) and when ("always active on any Golang coding, review, debug, or setup task") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage ("Golang coding, review, debug, or setup task", "writing a gRPC service", "debugging a panic", "auditing security") but missing synonyms (Go vs Golang) and file extensions (.go) that users commonly say.	4 / 5
Distinctiveness Conflict Risk	Clear niche as the orchestrator for the samber/cc-skills-golang family with distinct Golang-task triggers; minimal conflict risk since it is explicitly a meta-routing skill over the leaf golang-* skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: samber/cc-skills-golang
Path: skills/golang-how-to/SKILL.md
Commit: 19a0626

Reviewed: 1 day 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.