unit-test-parameterized
Parameterized testing patterns with @ParameterizedTest, @ValueSource, @CsvSource. Run single test method with multiple input combinations. Use when testing multiple scenarios with similar logic.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill unit-test-parameterized82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%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 is a well-crafted skill description that clearly identifies its specific domain (JUnit parameterized testing) with concrete annotations and includes an explicit 'Use when' clause. The main weakness is that trigger terms lean heavily on technical annotation names rather than natural language users might use when seeking this functionality.
Suggestions
Add natural language trigger terms users might say, such as 'data-driven testing', 'test with different inputs', 'test multiple values', or 'JUnit parameterized tests'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: parameterized testing patterns with specific annotations (@ParameterizedTest, @ValueSource, @CsvSource), running single test methods with multiple input combinations. | 3 / 3 |
Completeness | Clearly answers both what (parameterized testing patterns with specific annotations, running tests with multiple inputs) and when ('Use when testing multiple scenarios with similar logic'). | 3 / 3 |
Trigger Term Quality | Includes technical terms like @ParameterizedTest, @ValueSource, @CsvSource which are accurate but may not be what users naturally say. Missing common variations like 'data-driven testing', 'test with different inputs', or 'JUnit parameterized'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on parameterized testing with JUnit-specific annotations. Unlikely to conflict with general testing skills or other testing frameworks due to the specific annotation references. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent executable code examples covering the full range of JUnit 5 parameterized testing patterns. The main weaknesses are moderate verbosity (the 'When to Use' section and some explanatory text could be trimmed) and the monolithic structure that could benefit from progressive disclosure to separate files for advanced patterns.
Suggestions
Remove or significantly condense the 'When to Use This Skill' section - Claude can infer appropriate usage from the examples
Consider moving advanced patterns (ArgumentsProvider, CsvFileSource, RepeatedTest) to a separate ADVANCED.md file with clear links
Trim the setup section - version numbers could be omitted as Claude knows to use current versions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary sections like 'When to Use This Skill' that Claude can infer, and the setup section with Maven/Gradle dependencies adds bulk that may not always be needed. The content could be tightened while preserving utility. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all snippets are copy-paste ready with proper imports, complete method signatures, and realistic test scenarios. The examples cover @ValueSource, @MethodSource, @CsvSource, @EnumSource, and custom ArgumentsProvider comprehensively. | 3 / 3 |
Workflow Clarity | For a parameterized testing skill, the workflow is inherently simple (write test, add annotation, provide data). The skill clearly sequences from basic patterns to advanced ones, and the troubleshooting section addresses common issues. No destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers progressing from basic to advanced, but it's a monolithic document that could benefit from splitting advanced patterns (ArgumentsProvider, CsvFileSource) into separate reference files. The References section links to external docs but no internal file structure. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | 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 | 12 / 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.