CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/proptest-testing

Authors property-based tests in Rust using proptest - wires the `proptest!` macro, defines strategies (`prop::collection::vec`, type-driven `any` strategies, regex-based string strategies), uses the strategy-per-value model (vs QuickCheck's per-type) for flexible composition, and exploits proptest's automatic shrinking + persistence of failed cases (regression test artifact). Use when a Rust codebase needs PBT - pairs especially well with parsers, serializers, and any function with a structured input domain.

75

Quality

94%

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%

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

A well-structured, highly actionable skill body with executable code, a clear feedback-loop workflow, and clean progressive disclosure to a single verified reference. Its main weakness is mild verbosity in the Overview where it quotes basic property-testing concepts.

Suggestions

Tighten the Overview blockquotes: drop the 'Proptest is a property testing framework...' restatement of concepts Claude already knows, keeping only the differentiator versus QuickCheck and the failure-persistence mechanism.

Trim prose between code blocks (e.g., the paragraph restating regex-based string generation right under the example) to reduce repetition with the strategy catalog.

DimensionReasoningScore

Conciseness

Mostly code-dense and lean, but the Overview blockquotes restate concepts Claude already knows ('automatically generates test inputs and shrinks failures', 'Strategy-based approach') that could be trimmed; it is not score-3 lean nor score-1 padded.

2 / 3

Actionability

Provides executable Cargo.toml, `proptest!` examples, a config block, a strategy catalog, a `prop_compose!` worked example, and an anti-pattern table with fixes — copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

The 'How to use' 7-step sequence and worked example include an explicit fail→shrink→commit-regression→fix→re-run feedback loop ('re-run cargo test ... replaying the saved seed first'), matching the score-3 anchor with validation checkpoints.

3 / 3

Progressive Disclosure

Body is an overview that delegates detail to one real, clearly-signaled, one-level-deep reference (references/strategies-and-patterns.md, verified to exist), with custom-strategy content appropriately split out.

3 / 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 highly specific, third-person description that covers concrete capabilities and an explicit trigger clause, with clear differentiation from sibling crates. It is concise and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('wires the `proptest!` macro', 'defines strategies', 'uses the strategy-per-value model', 'exploits automatic shrinking + persistence'), matching the score-3 anchor rather than the partial score-2 anchor.

3 / 3

Completeness

Explicitly answers both what (authors/wires/defines/exploits) and when ('Use when a Rust codebase needs PBT - pairs especially well with parsers, serializers'), so it does not cap at 2 like a missing-trigger description.

3 / 3

Trigger Term Quality

Covers natural terms a user needing this would say — 'property-based tests', 'Rust', 'proptest', 'PBT', 'parsers, serializers', 'structured input domain' — rather than only jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (proptest in Rust) with explicit QuickCheck differentiation and distinct triggers, making overlap with other skills unlikely.

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