rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%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.

The body is highly actionable and concise with a clear TDD workflow and validation feedback loops, but it is a long monolithic file with no external references to offload detail, limiting progressive disclosure.

Suggestions

Split the larger reference material (Criterion benchmarking setup, full GitHub Actions CI config, detailed proptest strategies) into separate files under references/ and link to them one level deep from the overview sections.

Trim the DO/DON'T Best Practices list to the most non-obvious items; several entries restate testing fundamentals Claude already knows.

Move the exhaustive cargo test command flag list into a short reference table or separate file, keeping only the most common commands inline.

Dimension	Reasoning	Score
Conciseness	Code-forward and assumes Claude's competence with no padding about what Rust or tests are; a few sections (How It Works, DO/DON'T lists) could be tightened slightly but are largely efficient.	4 / 5
Actionability	Fully executable, copy-paste-ready Rust code and cargo commands throughout, covering unit, integration, async, property-based, mocking, doc tests, benchmarking, coverage, and CI for the common cases.	5 / 5
Workflow Clarity	The TDD RED-GREEN-REFACTOR cycle is a clearly sequenced workflow with explicit validation checkpoints ("Run tests (RED) — Verify the test fails", "Implement (GREEN)") and a feedback loop between failure and passing.	5 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but at ~500 lines everything is inlined into a single monolithic SKILL.md with no one-level-deep references splitting out content that could live separately (e.g., full CI config, benchmarking guide).	3 / 5
	Total	17 / 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.

The description is strong: it names comprehensive concrete capabilities, supplies explicit 'Use when' trigger phrasing, and occupies a distinct Rust-testing niche. Minor gap is the omission of benchmarking/doctest terms from the trigger list.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "unit tests, integration tests, async testing, property-based testing, mocking, and coverage" plus "Follows TDD methodology" — giving comprehensive coverage rather than a single vague action.	5 / 5
Completeness	Explicitly states both what ("Rust testing patterns including ... mocking, and coverage. Follows TDD methodology") and when ("Use when writing Rust tests — ..."), matching the anchor for clear concrete triggers.	5 / 5
Trigger Term Quality	Includes natural phrases users say ("Use when writing Rust tests — unit, integration, async, property-based, or coverage") with good keyword coverage, but omits terms like benchmarks and doctests that appear in the body.	4 / 5
Distinctiveness Conflict Risk	Scoped specifically to Rust testing with a distinct trigger ("Rust tests"), occupying a clear niche with minimal overlap risk against other skills.	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
skill_md_line_count	SKILL.md is long (502 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/rust-testing/SKILL.md
Commit: d8409a4

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.