golang-stretchr-testify

Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification, suite lifecycle, and advanced patterns like Eventually, JSONEq, and custom matchers. Apply when the codebase imports github.com/stretchr/testify.

1.37x

Quality

89%

Does it follow best practices?

Impact

84%

1.37x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

79%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, well-structured testify reference skill with excellent actionability and conciseness. The code examples are realistic and executable, the common mistakes section adds genuine value, and the assert/require distinction is clearly explained with a practical rule. The main weaknesses are the inline length of the assertions reference (which could be split out) and the missing bundle file for the referenced mock.md.

Suggestions

Move the detailed Core Assertions and Advanced Assertions sections into a separate reference file (e.g., references/assertions.md) and keep only the most essential examples inline

Ensure the referenced ./references/mock.md file exists in the bundle to support the progressive disclosure pattern

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient throughout. It assumes Claude knows Go and testing concepts, avoids explaining what testify is beyond one orienting sentence, and uses code examples as the primary teaching mechanism. The persona/modes section at the top is slightly unnecessary but very brief.	3 / 3
Actionability	All code examples are fully executable Go code, not pseudocode. The assertions reference, mock patterns, suite lifecycle, and common mistakes sections all provide concrete, copy-paste-ready guidance with specific function signatures and realistic usage patterns.	3 / 3
Workflow Clarity	The skill clearly sequences the assert vs require decision and the suite lifecycle, but it's primarily a reference skill rather than a multi-step workflow. The mock section delegates to a reference file without showing the full workflow (define mock → set expectations → call → verify), and there's no explicit validation/verification workflow for writing tests end-to-end.	2 / 3
Progressive Disclosure	The skill references `./references/mock.md` for detailed mock content and cross-references other skills, which is good structure. However, the bundle has no files, so the mock reference is unverifiable. The core assertions section is quite long inline and could benefit from being split into a reference file, while the main SKILL.md keeps a concise overview.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

This is an excellent skill description that clearly identifies its domain (Go testify library), lists specific capabilities across multiple packages, and provides explicit trigger conditions including both user intent scenarios and codebase detection signals. It uses proper third-person voice throughout and balances comprehensiveness with clarity.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and concepts: assert, require, mock, suite packages, testify assertions, mock expectations, argument matchers, call verification, suite lifecycle, and advanced patterns like Eventually, JSONEq, and custom matchers.	3 / 3
Completeness	Clearly answers both 'what' (comprehensive guide covering assert, require, mock, suite packages with specific features) and 'when' (explicit 'Use when writing tests with testify, creating mocks, setting up test suites' and 'Apply when the codebase imports github.com/stretchr/testify').	3 / 3
Trigger Term Quality	Excellent coverage of natural terms a Go developer would use: 'testify', 'assert', 'require', 'mock', 'test suites', 'Golang testing', 'github.com/stretchr/testify', 'assertions', 'mock expectations', 'argument matchers'. These are all terms users would naturally mention.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — narrowly scoped to the stretchr/testify library for Go, with specific package names and import path. Unlikely to conflict with general Go testing skills or other language testing skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: samber/cc-skills-golang
Commit: a5e0e59

Reviewed: 14 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.