property-based-testing

What it does

The package's scoped documentation describes three distinct jobs: writing properties, reviewing tests that may assert too little, and diagnosing a minimized failing example. It names established testing libraries for Python, JavaScript, Rust and other ecosystems. The bundled skill supplies workflow guidance; the testing libraries and target code remain separate dependencies.

Best for

A developer with parsers, serializers, validators or state transitions whose expected invariants can be written down. It is useful when example tests cover only a few inputs and the team can investigate a generated counterexample.

Tradeoffs

A generated property may encode the wrong specification. More executions do not make an incorrect property useful. The publisher also documents evaluation harnesses that can spend API budget; those are optional source tooling, not something this catalog executes or a requirement for browsing the listing.

A practical first task

Choose one pure function and state a round-trip or normalization property before generating tests. Run the chosen testing library on synthetic input in your own project environment and preserve the smallest failing case for review.

What to validate

Introduce a known defect and check that the property detects it. Then review whether a failure is a product bug, an ambiguous requirement or a bad property. No upstream evaluation scripts, test libraries or paid model calls were run for this assessment.

Compatibility

claude-code

Publisher manifest for claude-code; runtime behavior not tested

Compatibility source

Installation and requirements

Claude Code for the detected plugin format, plus the appropriate property-testing library in the project you choose to test. Upstream evaluation harnesses can spend API budget and are optional.

The scoped README documents this interactive marketplace path; select the property-based-testing package. No upstream harness or package was executed.

/plugin marketplace add trailofbits/skills

/plugin menu

Open the pinned package below and follow its publisher instructions for your agent. A Skills installer is not a universal plugin installer. Review hooks, bundled MCP connections, permissions and configuration before enabling the package.

Detected formats

• .claude-plugin/plugin.json — plugins/property-based-testing/.claude-plugin/plugin.json

Bundled components

Skills Declared

No

Mcp Declared

No

Hooks Declared

No

Skills Present

Yes

Mcp Config Present

No

Hooks Present

No

Apps Declared

No

Presence is a static file/manifest observation. A missing declaration does not prove the component is absent at runtime.

Read publisher setup ↗

Unknown; source software and connected services may have separate terms.