Name: golang-testing
Rating: 78 (1 reviews)
Author: samber

golang-testing

Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see `samber/cc-skills-golang@golang-stretchr-testify`; for measurement methodology see `samber/cc-skills-golang@golang-benchmark`.

1.00x

Quality

89%

Does it follow best practices?

Impact

75%

1.00x

Average score across 1 eval scenario

Securityby

Passed

No findings from the security scan

Quality

Content

86%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, highly actionable Go testing skill with executable examples throughout and clean progressive disclosure to real reference files. The main improvements are trimming the redundant summary section and making workflow validation checkpoints explicit rather than implied.

Suggestions

Collapse or remove the 'Best Practices Summary' list — its 13 items are restated in the detailed sections that follow, so it primarily costs tokens.

Add explicit validation checkpoints to Write and Debug modes (e.g. 'run go test and confirm PASS before enriching edge cases' / 're-run until the failure reproduces deterministically before tracing') to close the implicit-checkpoint gap.

Tighten the source-file-naming rationale paragraphs; the core rule is valuable but the 'because tools... resolve tests by source file' explanation restates Go conventions Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's Go knowledge, but the 13-item 'Best Practices Summary' restates later sections and a few explanatory rationales (e.g. the source-file-naming justification) could be trimmed.	4 / 5
Actionability	Abundant copy-paste-ready Go code and shell commands across table-driven tests, goleak, synctest, benchmarks, fuzzing, coverage, and a Quick Reference of go-test invocations, covering the common cases fully.	5 / 5
Workflow Clarity	Four modes (Write/Review/Audit/Debug) give clear sequences (e.g. Debug: 'reproduce reliably, isolate the failing assertion, trace the root cause'), but validation checkpoints are mostly implicit rather than explicit validate-fix-retry loops.	4 / 5
Progressive Disclosure	The body is an overview with well-signaled one-level-deep references — all four ./references/*.md links resolve to real files — and explicit cross-references to sibling skills, with detail appropriately split into the reference files.	5 / 5
	Total	18 / 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, third-person description that clearly states what the skill does and when to use it, with concrete trigger phrases and explicit delegation to sibling skills to avoid overlap. Only minor keyword-variation gaps keep trigger-term quality just below a perfect score.

Dimension	Reasoning	Score
Specificity	Enumerates a comprehensive set of concrete actions — 'table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming' — matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated test types) and 'when' via the concrete 'Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests' clause.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'writing or reviewing Go tests', 'flaky/slow tests', and 'Go test CI' are present, but coverage stops short of the synonym-and-variation breadth of a 5 (e.g. 'unit tests' absent from the trigger clause).	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Golang-testing niche and explicitly delegates overlapping concerns to sibling skills ('for testify-specific APIs see...', 'for measurement methodology see...'), minimizing conflict risk.	5 / 5
	Total	19 / 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-testing/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.