property-based-test-helper
Property Based Test Helper - Auto-activating skill for Test Automation. Triggers on: property based test helper, property based test helper Part of the Test Automation skill category.
34
0%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/property-based-test-helper/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It fails on all dimensions: it describes no concrete actions, includes no natural trigger terms (just the skill name duplicated), provides no 'Use when...' guidance, and is indistinguishable from any other testing-related skill. It needs a complete rewrite.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates property-based tests using frameworks like Hypothesis or QuickCheck, defines custom generators, writes invariant properties, and configures shrinking strategies.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about property-based testing, writing generators, QuickCheck, Hypothesis, fuzz testing, invariant checking, or randomized test inputs.'
Remove the duplicated trigger term and replace with diverse natural keywords users would actually say, such as 'property testing', 'generative testing', 'test properties', 'shrinking', 'arbitrary instances', '.prop files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only names itself ('Property Based Test Helper') and its category ('Test Automation') without describing what it actually does—no mention of generating properties, shrinking test cases, writing generators, or any other specific capability. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of capabilities beyond the generic category label 'Test Automation'. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('property based test helper, property based test helper'). There are no natural user keywords like 'property testing', 'hypothesis', 'QuickCheck', 'generators', 'invariants', 'fuzzing', or 'shrinking' that a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic that it could easily conflict with any other testing-related skill. 'Test Automation' is a broad category, and without specific triggers or capability descriptions, there is nothing to distinguish this from unit testing, integration testing, or other test helper skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It consists entirely of generic boilerplate that describes what the skill would do without providing any actual guidance on property-based testing. There are no code examples, no library-specific instructions (Hypothesis, fast-check, etc.), no strategies, no property definitions, and no actionable content of any kind.
Suggestions
Add concrete, executable code examples for property-based testing using specific libraries (e.g., Hypothesis for Python, fast-check for JS) showing how to define properties, generators, and shrinking strategies.
Define a clear workflow: 1) Identify properties to test, 2) Write generators for input data, 3) Define property assertions, 4) Run and interpret results, 5) Handle shrunk failing cases.
Remove all boilerplate meta-descriptions ('This skill provides automated assistance...') and replace with actual technical content about property-based testing patterns, common pitfalls, and when to use PBT vs example-based tests.
Add specific examples of common property types (roundtrip/encode-decode, invariants, idempotency, commutativity) with copy-paste ready test code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the phrase 'property based test helper' excessively, and provides zero actual technical content about property-based testing. | 1 / 3 |
Actionability | There are no concrete code examples, no specific commands, no library recommendations (e.g., Hypothesis, fast-check), and no executable guidance whatsoever. The content only describes what the skill claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to external files, no structured sections with real content, and no navigation to deeper materials. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- Reviewed
Table of Contents
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.