agentsclimarketplace

Testing property based

Skill planifest/planifest-framework/planifest-framework/external-skills/testing-property-based

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill testing-property-based

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Property-based testing workflow for invariant validation over broad input spaces. Use when correctness depends on rules that must hold across many generated inputs; do not use for narrow deterministic examples only.

SKILL.md

1.9 KB, as published. Nobody here has run it

Testing Property-Based

Overview

Use this skill to validate invariants beyond hand-picked test cases by combining generators, shrinking, and reproducible seeds.

Scope Boundaries

  • Use when input space is large and example-based tests are insufficient.
  • Typical requests:
    • Verify encode/decode roundtrip invariants for arbitrary inputs.
    • Stress aggregate invariants with generated data.
    • Catch edge cases that fixed examples miss.
  • Do not use when:
    • A small deterministic unit test set is sufficient (testing-unit).
    • The primary scope is UI journey validation (testing-e2e).

Inputs

  • Invariants and domain constraints
  • Generator strategy and seed reproducibility requirements
  • Runtime budget and flaky-risk tolerance

Outputs

  • Property definitions and generator coverage strategy
  • Decision record for shrinking and seed policy
  • Verification checklist with failing-case reproduction guidance

Workflow

  1. Formalize invariants and invalid-state assumptions.
  2. Design generators that reflect realistic and adversarial inputs.
  3. Compare generation/shrinking strategies and choose one.
  4. Run property tests with reproducible seeds.
  5. Triages failures with shrunk counterexamples and publish fixes.

Quality Gates

  • Core invariants are explicit and testable.
  • Generators cover edge and adversarial shapes.
  • Failures are reproducible via seed and shrunk case.
  • Residual unknowns are documented.

Failure Handling

  • Stop when invariants are undefined or contradictory.
  • Escalate when generator quality is too weak for meaningful coverage.

Bundled Resources

  • references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.