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.59x

Quality

86%

Does it follow best practices?

Impact

91%

1.59x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

72%

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

A high-quality, code-dense reference skill with strong actionability and good progressive disclosure that pushes mock detail to a real reference file. It is slightly held back by mild redundancy in prose and the absence of an explicit sequenced workflow, though neither is critical for a reference-style skill.

Suggestions

Tighten the opening paragraph and 'Covers' restatements to avoid echoing the frontmatter description and save tokens.

For the Write and Review modes, add a short sequenced checklist (e.g., identify unit under test -> write/audit assertions -> verify mocks with AssertExpectations) to give the body a clearer procedural spine.

Consider a one-line validation checkpoint reminder near mock/suite examples (e.g., always run AssertExpectations before the test ends) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly code-first and efficient, but the opening summary paragraph and some 'Covers' restatements echo the frontmatter description and could be tightened; a few sentences do not strictly earn their tokens.	2 / 3
Actionability	Extensive executable Go with real signatures and complete examples (TestParseConfig, Eventually/EventuallyWithT, full suite with launcher, mock matchers) — copy-paste ready and specific.	3 / 3
Workflow Clarity	Clear rules and unambiguous mode guidance (assert vs require, argument order, required suite.Run launcher), but as a multi-package reference it lacks an explicit sequenced procedural spine with validation checkpoints.	2 / 3
Progressive Disclosure	Body is a well-organized overview that offloads the heavy mock material to a real one-level-deep reference ([Mock reference](./references/mock.md), verified present), with a Cross-References section for sibling skills.	3 / 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.

A strong, specific description in third person that clearly states what the skill covers and gives explicit, library-specific trigger conditions. It is comprehensive without being vague and is unlikely to conflict with sibling skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across packages — 'Covers assert, require, mock, and suite packages', 'creating mocks, setting up test suites', and advanced patterns like 'Eventually, JSONEq, and custom matchers'.	3 / 3
Completeness	Explicitly answers both what ('Comprehensive guide to stretchr/testify... Covers assert, require, mock, and suite packages') and when ('Use when writing tests with testify...' and 'Apply when the codebase imports github.com/stretchr/testify').	3 / 3
Trigger Term Quality	Natural phrasings a Go developer would say are well covered: 'writing tests with testify', 'creating mocks', 'setting up test suites', 'choosing between assert and require', and the import-path trigger 'github.com/stretchr/testify'.	3 / 3
Distinctiveness Conflict Risk	The niche is the specific testify library and the trigger is tied to its import path, making it unlikely to fire for unrelated Go testing skills.	3 / 3
	Total	12 / 12 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-stretchr-testify/SKILL.md
Commit: 4158351

Reviewed: about 13 hours 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.