CtrlK
BlogDocsLog inGet started
Tessl Logo

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`.

85

1.06x
Quality

93%

Does it follow best practices?

Impact

82%

1.06x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

The body is a strong, actionable testing guide: executable code throughout, clean mode-based structure, and disciplined progressive disclosure to reference files. Its main weakness is minor verbosity in a few explanatory passages and implicit rather than explicit validation checkpoints.

Suggestions

Trim the rationale prose in 'File Conventions' (the explanation of why tools resolve tests by source file) to a one-line justification; the convention itself is what matters.

Add an explicit validation/retry checkpoint to Review or Debug mode (e.g., 'after fixing, re-run `go test -race` and confirm green before moving on') to make feedback loops concrete.

Move the 'testing/synctest' Go-version detail table or the version-gated API guidance into a reference file, since the version-specific notes (1.25/1.26/1.27) are time-sensitive and weigh the overview down.

DimensionReasoningScore

Conciseness

Mostly lean with dense code examples and terse commentary, but a few sections over-explain rationale a competent Go engineer already knows (e.g., justifying the one-test-file-per-source-file convention at length), keeping it just below fully efficient.

4 / 5

Actionability

Provides numerous complete, executable Go code blocks (table-driven tests, goleak TestMain, synctest, fuzzing, t.Parallel, ArtifactDir) and a copy-paste Quick Reference of bash commands covering the common cases.

5 / 5

Workflow Clarity

Four modes (Write/Review/Audit/Debug) each define a clear sequence, but validation checkpoints are mostly implicit rather than written as explicit validate→fix→retry loops, leaving minor validation gaps.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references (e.g. 'See [HTTP Testing](./references/http-testing.md)'), all referenced files verified present, with detailed patterns appropriately split into reference files for easy navigation.

5 / 5

Total

18

/

20

Passed

Description

100%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 comprehensive and well-structured: it enumerates concrete capabilities, provides explicit 'Use when' trigger guidance, and scopes itself distinctly from sibling skills. Voice is third-person throughout, consistent with the rubric's guidance.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities comprehensively — '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 anchor for comprehensive coverage of specific actions.

5 / 5

Completeness

Explicitly answers both what ('Production-ready Golang tests — ...') and when ('Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users say ('writing or reviewing Go tests', 'debugging flaky/slow tests', 'setting up Go test CI', 'fuzzing', 'integration tests') with synonyms, matching comprehensive trigger coverage.

5 / 5

Distinctiveness Conflict Risk

Scoped tightly to Go testing with specific tooling (goleak, testify, gotests) and explicitly defers overlapping concerns to sibling skills via cross-references, giving it a clear niche with minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
samber/cc-skills-golang
Reviewed

Table of Contents

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.