CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/go-rust-mocking

Isolates dependencies in Go and Rust unit tests using test-double generation - Go: `go.uber.org/mock` (gomock + mockgen codegen) and `github.com/stretchr/testify/mock` (hand-written stubs); Rust: `mockall` crate with `#[automock]` for traits and `mock!` macro for structs and external traits. Use when a unit test reaches a database, HTTP client, file system, or any interface boundary that must be replaced with a controlled fake to keep tests fast, deterministic, and isolated.

77

Quality

97%

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

Overview
Quality
Evals
Security
Files

Quality

Content

92%

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

A high-quality, actionable reference with executable code, clear per-tool workflows, and explicit verification guidance. Its main gap is progressive disclosure: everything lives inline in one large SKILL.md with no bundled reference files to keep the overview lean.

Suggestions

Move the gomock matcher table and mockall expectation-methods table into a bundled reference file (e.g. references/matcher-reference.md) and link to it from SKILL.md so the overview stays lean.

Add a concise decision/quick-start table near the top pointing readers to the per-tool sections, so SKILL.md reads as an overview hub rather than a flat catalog.

Consider splitting the full per-tool worked examples into separate reference files linked from a brief summary, keeping only the gomock-vs-testify-vs-mockall decision guidance and one minimal example inline.

DimensionReasoningScore

Conciseness

Reference-dense and lean: install commands, complete code blocks, and matcher/method tables earn their tokens; only a single brief 'test double' definition leans toward concepts Claude already knows.

3 / 3

Actionability

Provides fully executable install commands, mockgen invocations, and complete Go/Rust test functions with real matchers and expectations — copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

Each tool follows a clear install->generate->write-test->verify sequence, with explicit verification mechanisms (auto-Finish, drop verification, AssertExpectations), anti-pattern reminders, and a CI 'go generate' drift loop.

3 / 3

Progressive Disclosure

Sections are well-organized and external URL references are clearly signaled one level deep, but no bundle files exist and all detailed reference material (matcher table, expectation-method catalog, full examples) is inline in a single ~340-line file rather than split out.

2 / 3

Total

11

/

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, information-dense description: it names concrete tools and approaches for both ecosystems and includes an explicit 'Use when' trigger covering common boundary types. It is specific, complete, and distinctive with no fluff.

DimensionReasoningScore

Specificity

Names multiple concrete tools and actions (gomock + mockgen codegen, testify hand-written stubs, mockall #[automock] and mock! macro) rather than vague language.

3 / 3

Completeness

Explicitly states what it does (isolates Go/Rust test dependencies via test doubles) and when to use it via an explicit 'Use when...' clause.

3 / 3

Trigger Term Quality

Covers natural terms users would say ('unit test', 'database', 'HTTP client', 'file system', 'mock', 'stub', 'fake') alongside the tool names.

3 / 3

Distinctiveness Conflict Risk

Scoped to Go and Rust unit-test mocking with specific named tools, giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents