CtrlK
BlogDocsLog inGet started
Tessl Logo

testify-tdd

Use this skill when writing Go tests with stretchr/testify, implementing TDD workflows, creating mocks, or organizing test suites. Covers assert vs require patterns, interface mocking, table-driven tests, and the red-green-refactor cycle.

67

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable, well-structured guide that is held back by verbosity and a monolithic single-file layout that inlines reference material. Splitting the API/mock references into bundled files and trimming introductory prose would improve it.

Suggestions

Move the 'Common Assertion Methods', 'Mock Argument Matchers', and 'Mock Return Values' reference blocks into separate files under references/ and link to them from SKILL.md to reduce inline bulk and improve progressive disclosure.

Trim explanatory prose about well-known concepts (e.g., what table-driven tests are, the TDD cycle intro) and keep only the testify-specific guidance to improve conciseness.

Add explicit validation/verification checkpoints (e.g., 'run go test ./... after each refactor; only proceed when green') to the TDD and mock workflows to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Mostly efficient code-heavy content, but includes explanatory prose Claude already knows ('The idiomatic Go pattern for testing multiple scenarios', TDD cycle exposition, 'Critical distinction: Choose based on whether the test should continue after failure') that could be trimmed.

3 / 5

Actionability

Provides abundant copy-paste-ready, executable Go examples covering assert/require, table-driven tests, mocking, suites, and the TDD cycle across the common cases.

5 / 5

Workflow Clarity

The TDD red-green-refactor section is a clearly numbered sequence with run-the-test feedback loops, but validation checkpoints are not emphasized uniformly across the other sections.

4 / 5

Progressive Disclosure

Section headers organize the content well, but this is a ~480-line single file with reference material (Common Assertion Methods, Mock Argument Matchers, Mock Return Values) inlined that would be better split into separate reference files.

3 / 5

Total

15

/

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, specific description with explicit 'what' and 'when' guidance and low conflict risk. Trigger-term coverage is good but could add a few more natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'writing Go tests with stretchr/testify', 'creating mocks', 'organizing test suites', 'assert vs require patterns', 'interface mocking', 'table-driven tests', and 'red-green-refactor cycle' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers 'when' via 'Use this skill when writing Go tests with stretchr/testify, implementing TDD workflows, creating mocks, or organizing test suites' and 'what' via 'Covers assert vs require patterns, interface mocking, table-driven tests, and the red-green-refactor cycle.'

5 / 5

Trigger Term Quality

Includes natural terms users would say ('Go tests', 'TDD workflows', 'mocks', 'test suites', 'testify'), but a few common synonyms like 'unit tests' or 'stubbing' are not surfaced in the description itself.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (testify-based Go testing with TDD) with distinct triggers, making conflict with unrelated skills minimal.

5 / 5

Total

19

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
freightCognition/linehaulai-claude-marketplace
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.