CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/proptest-testing

Use for any question or task about property-based or generated-input tests in Rust, including quick how-to questions, round-trip checks and parsers that crash on fuzzed input: proptest with the proptest! macro, strategies for collections, regex strings and any, shrinking, and the persisted regression file.

Quality

92%

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

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.

Highly actionable and well-structured: executable code throughout, a sequenced workflow with an explicit failure-recovery loop, and proper use of a single clearly-signaled reference file. The main cost is token efficiency — the conceptual Overview and repeated regression-file/maintenance notes could be trimmed without losing anything Claude doesn't already know.

Suggestions

Cut or compress the Overview's README quotes (what proptest is, the quickcheck comparison) — keep only the non-obvious operational facts, e.g. that the regression file is replayed before new cases are generated.

State the 'commit proptest-regressions/ to git' guidance once in the Failure persistence section and reference it from How to use, the worked example, and the anti-patterns table instead of repeating it; likewise merge the duplicated 'passive maintenance' notes from Install and Limitations.

Trim the anti-patterns table entries whose fixes merely restate other sections (e.g. the prop_assert! and PROPTEST_SEED rows) to one-line pointers.

DimensionReasoningScore

Conciseness

The Overview section quotes the README to explain what proptest is and how it differs from quickcheck ("the key differentiator from Rust's quickcheck crate") — background Claude already knows — and guidance is repeated ("Commit this file to git" appears in Failure persistence, How to use step 6, the worked example, and the anti-patterns table; the "passive maintenance" note appears in both Install and Limitations). This fits "mostly efficient but includes some unnecessary explanation or could be tightened" rather than 4's "minor instances".

3 / 5

Actionability

Guidance is fully executable and copy-paste ready: the Cargo.toml dev-dependency, a complete proptest! property, a ProptestConfig block, CI yaml with PROPTEST_SEED, a prop_compose! definition, and concrete strategy/config/anti-pattern tables cover the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

"How to use" gives a clear 7-step sequence with an explicit error-recovery feedback loop — "Run cargo test; on failure, commit the generated proptest-regressions/ file" and, in the worked example, "Fix from_hex() to accept lowercase; re-run cargo test and the property passes" — matching the 5 anchor's validation steps and feedback loops.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview whose deep material (prop_compose! and the round-trip/invariant/equivalence patterns) lives in the real, one-level-deep references/strategies-and-patterns.md, signaled with purpose text at each mention and catalogued in the References section — matching the 5 anchor's clear split and easy navigation.

5 / 5

Total

18

/

20

Passed

Description

96%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 with an explicit, concrete trigger clause, natural synonym coverage, and a specific scope list spanning the macro, strategies, shrinking, and regression files. The only weakness is slight overlap risk with sibling property-testing/fuzzing skills from the generic "generated-input" and "fuzzed input" phrasing.

DimensionReasoningScore

Specificity

The description lists multiple concrete items — "round-trip checks and parsers that crash on fuzzed input", "the proptest! macro", "strategies for collections, regex strings and any, shrinking, and the persisted regression file" — comprehensively covering the skill's scope, matching the 5 anchor rather than 4, which presumes coverage gaps.

5 / 5

Completeness

Both halves are explicit: an explicit trigger clause ("Use for any question or task about property-based or generated-input tests in Rust, including quick how-to questions...") and a concrete scope list after the colon; this exceeds the 4 anchor, where the 'when' is less explicit or specific.

5 / 5

Trigger Term Quality

Natural user phrasing is well covered with synonyms — "property-based", "generated-input", "fuzzed input" — alongside "round-trip checks", "shrinking", and "proptest" itself; no natural variation a user would say is missing (there are no file extensions to cite for a test framework).

5 / 5

Distinctiveness Conflict Risk

The Rust + proptest scope is a clear niche, but "generated-input tests" and "parsers that crash on fuzzed input" carry minor overlap risk with the closely related quickcheck/fuzzing sibling skills the bundle itself references, fitting the 4 anchor ("mostly distinct; minor overlap risk") better than 5's "minimal conflict risk".

4 / 5

Total

19

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page