rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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 Rust testing reference with executable examples and a clear TDD workflow. Its weaknesses are token redundancy from restating well-known concepts and a monolithic structure that would benefit from splitting detailed topics into reference files.

Suggestions

Trim the redundant RED/GREEN/REFACTOR explainer box and basic macro labels, which restate concepts Claude already knows.

Split large standalone topics (e.g. MOCKING.md, PROPTES.md, BENCHMARKING.md) into one-level-deep reference files linked from a concise overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and code-heavy, but the ~500-line body restates concepts Claude already knows (the RED/GREEN/REFACTOR box) and labels basic macros ("Equality", "Inequality"), so it could be tightened rather than earning the lean score-3 anchor.	2 / 3
Actionability	Provides abundant executable, copy-paste-ready code and commands across unit, integration, async, rstest, proptest, mockall, criterion, coverage, and CI — fully concrete and specific.	3 / 3
Workflow Clarity	The TDD workflow is a clearly sequenced 7-step process with an explicit RED verification checkpoint ("Verify the test fails with the expected error") and an inherent RED→GREEN feedback loop, satisfying the score-3 anchor.	3 / 3
Progressive Disclosure	Sections are well-organized, but the entire ~500-line skill is a single monolithic file with no reference files for sizable topics (mocking, proptest, benchmarking, CI) that could be split out — matching the score-2 anchor where content that should be separate is inline.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 specific, well-targeted description that names concrete Rust testing capabilities with natural trigger terms. Its main weakness is the absence of an explicit "Use when…" trigger clause, which leaves the 'when to use' guidance implied rather than stated.

Suggestions

Append an explicit trigger clause, e.g. "Use when writing or adding tests to Rust code, or when the user mentions Rust unit/integration tests, mocking, coverage, or TDD."

Consider adding natural phrasing variations users might say (e.g. "cargo test", "test coverage", "property tests") to broaden trigger matching.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete testing capabilities — "unit tests, integration tests, async testing, property-based testing, mocking, and coverage" — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Clearly answers what the skill does, but lacks any "Use when…" or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2; "Follows TDD methodology" is a methodology note, not a trigger.	2 / 3
Trigger Term Quality	Uses natural terms a user would say (unit tests, integration tests, mocking, coverage, TDD) with good coverage and common variations, rather than opaque jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped specifically to Rust testing with distinct terminology, forming a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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
skill_md_line_count	SKILL.md is long (501 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Commit: 4130457

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.