CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/rust-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 dense, example-driven reference with mostly executable Rust patterns and a clearly sequenced TDD workflow with validation checkpoints. Its weaknesses are redundancy in the TDD exposition, a fully monolithic structure with no reference files despite covering ~10 distinct topics, and a few missing dependency declarations for the showcased crates.

Suggestions

Move the advanced sections (mockall trait mocking, proptest custom strategies, criterion benchmarking, and CI integration) into separate reference files (e.g. references/mocking.md, references/proptest.md, references/ci.md) and link to them from SKILL.md to improve progressive disclosure and shrink the always-loaded context.

Remove the duplicated TDD exposition — either the "How It Works" steps or the "TDD Workflow for Rust" section with its RED-GREEN-REFACTOR diagram — and trim the trivial todo!() add() examples and the boilerplate fibonacci benchmark, since they re-explain concepts Claude already knows.

Add the missing Cargo.toml dev-dependency entries for rstest, proptest, and mockall (criterion's is already shown) so the showcased patterns are directly copy-paste runnable.

DimensionReasoningScore

Conciseness

The body is mostly efficient code examples with no tutorial padding, but the TDD sequence is stated twice ("How It Works" steps 4-6 and again in the "TDD Workflow for Rust" section with the RED-GREEN-REFACTOR diagram), the trivial todo!() examples explain TDD basics Claude already knows, and the canonical fibonacci Criterion benchmark is boilerplate — matching anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened').

3 / 5

Actionability

Nearly all examples are executable, complete Rust with concrete commands (cargo test variants, cargo llvm-cov flags, a full CI yaml), but dev-dependency declarations are shown only for criterion while rstest, proptest, and mockall usage appears without the corresponding Cargo.toml entries — a minor gap placing it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

The 7-step "How It Works" sequence is clear and includes explicit validation checkpoints ("Run tests (RED) — Verify the test fails with the expected error", coverage target 80%+), but there is no explicit error-recovery feedback loop for unexpected failures — anchor 4's 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

No bundle files exist and the ~495-line body is fully inline with zero references; well-organized sections exist, but content that belongs in separate files (the mockall guide, proptest custom strategies, criterion benchmarking, and CI integration) is inlined in SKILL.md — matching anchor 3 ('some structure but could be better organized... content that should be separate is inline').

3 / 5

Total

14

/

20

Passed

Description

87%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 description that explicitly states what the skill covers and when to use it, with natural trigger terms and a distinct Rust-testing niche. The only weaknesses are that capability areas are enumerated as topics rather than actions and a few natural synonyms (benchmarking, doc tests) are missing.

DimensionReasoningScore

Specificity

Lists six concrete capability areas ("unit tests, integration tests, async testing, property-based testing, mocking, and coverage") but these are subtopics rather than actions, and benchmarking/doc tests covered in the body are absent — matching anchor 4 ('several specific actions; minor gaps in coverage') rather than anchor 5's comprehensive coverage.

4 / 5

Completeness

Clearly answers both 'what' ("Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage") and 'when' ("Use when writing Rust tests — unit, integration, async, property-based, or coverage") with concrete trigger phrases in third person, matching the anchor-5 example.

5 / 5

Trigger Term Quality

Good natural-keyword coverage ("Rust tests", "unit", "integration", "async", "property-based", "coverage") that users would actually say, but missing common variations and synonyms such as "benchmarking", "doc tests", "test coverage", or file references like ".rs"/"Cargo.toml" — above anchor 3, short of anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

"Rust testing" is a clear niche with distinct, language-specific triggers (Rust, cargo, unit/integration/property-based tests); it is unlikely to fire for non-Rust or non-testing skills, matching anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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