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

Quality

89%

Does it follow best practices?

Impact

81%

1.92x

Average score across 3 eval scenarios

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, executable reference for testify with copy-paste Go examples, a clear assert/require decision rule, a common-mistakes checklist, and a real one-level-deep mock.md reference. Slight conciseness overhead from persona/modes framing is the only drag.

Dimension	Reasoning	Score
Conciseness	The body is lean — topical sections, executable snippets, and offloaded detail — with only mild overhead like the 'Persona' / 'Modes' framing and one orienting sentence about testing.T; not quite the every-token-earns-its-place of anchor 5.	4 / 5
Actionability	Multiple copy-paste-ready Go examples cover the common cases (assert/require setup, core + advanced assertions, mock wiring, suite launcher), and the assert-vs-require 'Rule' gives a concrete decision procedure, matching the anchor 5 fully-executable example.	5 / 5
Workflow Clarity	Clear decision rules ('require for preconditions, assert for verifications') and a 'Common Mistakes' review checklist supply sequence-like guidance with most checkpoints present; no explicit validate→fix→retry loop, but the skill is non-destructive so the destructive-cap does not apply and a 5 is not warranted without a fuller multi-step workflow.	4 / 5
Progressive Disclosure	Well-organized overview with a clearly signaled one-level-deep reference to the existing ./references/mock.md, plus cross-references to sibling skills (godig, gopls, golang-testing, golang-lint); bulk mock detail is appropriately split out, matching the anchor 5 navigation pattern.	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 concretely enumerates testify capabilities and provides explicit 'Use when' / 'Apply when' triggers anchored by the library import path. Only minor trigger-synonym coverage keeps it from a perfect sweep.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across packages — 'writing tests with testify, creating mocks, setting up test suites', plus 'mock expectations, argument matchers, call verification, suite lifecycle' and 'Eventually, JSONEq, and custom matchers' — comprehensive coverage, matching the anchor 5 example.	5 / 5
Completeness	Explicitly answers both what ('Covers assert, require, mock, and suite packages... assertions, mock expectations...') and when ('Use when writing tests with testify... Apply when the codebase imports github.com/stretchr/testify'), matching the anchor 5 example with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural triggers — 'writing tests with testify', 'creating mocks', 'setting up test suites', 'choosing between assert and require' plus the import-path trigger — but a few natural variations (e.g. 'mocking', 'test doubles', 'table-driven tests') are absent, so it sits just below the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche scoped to the testify library, anchored by the explicit import-path trigger ('Apply when the codebase imports github.com/stretchr/testify'), giving minimal overlap risk even against a general golang-testing skill.	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-stretchr-testify/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.