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 that provides no useful information for skill selection. It repeats the skill name as its only trigger term, describes no concrete actions, and lacks any 'Use when...' guidance. It would be nearly impossible for Claude to correctly select this skill from a pool of testing-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates property-based tests using randomized inputs, defines custom generators, writes invariant assertions, and configures shrinking strategies for failing cases.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about property-based testing, QuickCheck-style tests, hypothesis testing, random input generation, fuzz testing, invariant checking, or shrinking test failures.'
Differentiate from other testing skills by specifying the unique niche, e.g., 'Focuses on property-based/generative testing as opposed to example-based unit tests or integration tests.'
| 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 | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill's own name repeated twice ('property based test helper'). There are no natural user keywords like 'property testing', 'hypothesis', 'QuickCheck', 'generators', 'shrinking', 'invariants', or 'fuzz testing' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any testing-related skill. Without specifying what property-based testing entails or how it differs from unit testing, integration testing, or other test automation skills, conflict risk is very high. | 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 placeholder with no substantive content. It contains only boilerplate descriptions of what the skill would theoretically do, without any actual guidance on property-based testing—no code examples, no library-specific instructions, no strategies for defining properties, generators, or shrinking. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for property-based testing using specific frameworks (e.g., Hypothesis for Python, fast-check for JS), including how to define properties, custom generators, and interpret shrunk counterexamples.
Define a clear workflow: 1) Identify invariants/properties, 2) Write generators, 3) Run tests, 4) Analyze shrunk failures, 5) Fix and re-run—with explicit validation at each step.
Remove all boilerplate filler ('This skill provides automated assistance...', 'Provides step-by-step guidance...') and replace with actual actionable content that Claude doesn't already know.
Add references to supporting files or examples for advanced topics like stateful property testing, custom shrinking strategies, or integration with specific test frameworks (Jest, pytest).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase excessively, and provides zero substantive information about property-based testing. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code examples, no specific commands, no library recommendations (e.g., Hypothesis, fast-check), no strategies or property definitions. It only describes what the skill would do in abstract terms. | 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 sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague marketing-style text with no references to supporting files, no structured sections with real content, and no navigation to deeper material. There are no bundle files to support it either. | 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
13d35b8
- 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.