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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill property-based-test-helperOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use it. The only distinguishing element is the phrase 'property based test' which is insufficient for Claude to make informed skill selection decisions.
Suggestions
Add specific actions the skill performs, e.g., 'Generates property-based tests using hypothesis/quickcheck patterns, creates generators for custom types, identifies invariants to test'
Include a 'Use when...' clause with natural trigger terms like 'Use when writing property-based tests, creating test generators, fuzzing inputs, testing invariants, or when user mentions hypothesis, quickcheck, or random testing'
Add file type or framework triggers such as 'pytest with hypothesis', 'ScalaCheck', 'fast-check', or language-specific property testing libraries
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Property Based Test Helper') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of generating tests, creating properties, validating invariants, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just the skill name repeated. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'property based test helper' repeated twice, which is the skill name itself. Missing natural terms users would say like 'hypothesis', 'quickcheck', 'fuzzing', 'random testing', 'invariants', 'generators', or specific framework names. | 1 / 3 |
Distinctiveness Conflict Risk | Being in the 'Test Automation' category and mentioning 'property based' provides some specificity, but without concrete actions or distinct triggers, it could easily conflict with other testing-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about property-based testing. It contains only generic placeholder text that could apply to any skill, with no concrete guidance, code examples, or specific information about property-based testing concepts like generators, shrinking, or hypothesis/fast-check usage.
Suggestions
Add concrete, executable code examples showing property-based testing with a specific framework (e.g., Hypothesis for Python or fast-check for JavaScript)
Include specific guidance on writing property generators, defining invariants, and handling shrinking/counterexamples
Provide a clear workflow for when to use property-based vs example-based tests, with decision criteria
Remove all generic boilerplate text and replace with actual property-based testing patterns and anti-patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are meaningless filler without actual content. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no specific commands, and no actual instructions for property-based testing. The skill describes what it could do rather than providing executable guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The content is entirely abstract with no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure pointing to detailed materials, no references to other files, and no organized sections with actual content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.