hypothesis-testing

Property-based testing with Hypothesis for discovering edge cases and validating invariants. Use when implementing comprehensive test coverage, testing complex logic with many inputs, or validating mathematical properties and invariants across input domains. Triggered by: hypothesis, property-based testing, @given, strategies, generative testing.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/hypothesis-testing/SKILL.md

Quality

Content

57%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 thorough, mostly executable Hypothesis reference, but it is verbose in pedagogical sections and monolithic rather than progressively disclosed. Splitting the strategy catalog and advanced patterns into referenced files and trimming explanatory content would raise both conciseness and progressive disclosure.

Suggestions

Move the built-in strategy catalog and combinator reference into a separate references/STRATEGIES.md and link to it one level deep, keeping SKILL.md as an overview.

Delete or condense the 'Core Concept' and closing 'Summary' sections, which restate what property-based testing is and what Hypothesis does — concepts Claude already knows.

Add an explicit testing workflow with a validation checkpoint (write property → run → if shrunk failure found, add @example regression → re-run until green) to make the feedback loop concrete.

Dimension	Reasoning	Score
Conciseness	The bulk is dense, useful reference material, but the 'Core Concept', 'When to Use vs Example-Based', and closing 'Summary' sections restate concepts Claude already knows and pad the token budget unnecessarily.	3 / 5
Actionability	Abundant copy-paste-ready code with imports, install commands, and config blocks; minor gaps stem from placeholder functions like process() and calculate_distance() that are left undefined.	4 / 5
Workflow Clarity	A rough sequence exists (install → configure → write properties → run in CI) and the debugging/shrinking sections imply a feedback loop, but there is no explicit validate-then-proceed workflow with checkpoints for the testing lifecycle.	3 / 5
Progressive Disclosure	Well-organized with clear section headers, but ~860 lines are monolithically inlined with no bundle files in references/scripts/assets; the strategy catalog and API detail could be split into one-level-deep reference files.	3 / 5
	Total	13 / 20 Passed

Description

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

The description is strong: third-person voice, explicit what/when structure, and concrete trigger terms. Main weakness is that the listed actions are use-case variations of one capability rather than distinct operations.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'discovering edge cases', 'validating invariants', 'testing complex logic with many inputs', 'validating mathematical properties' — but they are variations of one capability rather than distinct operations, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Property-based testing with Hypothesis for discovering edge cases and validating invariants') and when ('Use when implementing comprehensive test coverage...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	'Triggered by: hypothesis, property-based testing, @given, strategies, generative testing' gives good natural keyword coverage including the library name and core concepts, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	The library name plus '@given', 'strategies', and 'property-based testing' carve a clear niche with minimal conflict, though 'implementing comprehensive test coverage' is broad enough to overlap with general testing skills.	4 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (873 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/hypothesis-testing/SKILL.md
Commit: d5ae560

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.