unit-test-boundary-conditions
Edge case and boundary testing patterns for unit tests. Testing minimum/maximum values, null cases, empty collections, and numeric precision. Pure JUnit 5 unit tests. Use when ensuring code handles limits and special cases correctly.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill unit-test-boundary-conditions80
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
77%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 solid skill description that clearly articulates specific testing patterns and includes an explicit 'Use when' clause. The main weaknesses are moderate trigger term coverage (missing common synonyms like 'corner cases') and potential overlap with other testing-related skills in a large skill library.
Suggestions
Add more trigger term variations like 'corner cases', 'boundary conditions', 'limit testing', 'off-by-one' to improve discoverability
Strengthen distinctiveness by explicitly contrasting with other testing types (e.g., 'Not for integration tests or mocking scenarios')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Testing minimum/maximum values, null cases, empty collections, and numeric precision.' Also specifies the technology: 'Pure JUnit 5 unit tests.' | 3 / 3 |
Completeness | Clearly answers both what ('Edge case and boundary testing patterns for unit tests. Testing minimum/maximum values, null cases, empty collections, and numeric precision. Pure JUnit 5 unit tests.') and when ('Use when ensuring code handles limits and special cases correctly.'). | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'edge case', 'boundary testing', 'minimum/maximum values', 'null cases', 'empty collections', but missing common variations users might say like 'corner cases', 'limit testing', 'edge conditions', or 'boundary conditions'. | 2 / 3 |
Distinctiveness Conflict Risk | While it specifies 'edge case and boundary testing' which is somewhat distinct, it could overlap with general unit testing skills or other JUnit testing skills. The niche is clear but not strongly differentiated from other testing-related skills. | 2 / 3 |
Total | 10 / 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 solid, actionable skill with excellent executable code examples covering comprehensive boundary testing scenarios. The main weakness is length - it could be more concise by removing sections that explain testing fundamentals Claude already knows, and by moving some detailed examples to referenced files. The code quality and coverage of edge cases is strong.
Suggestions
Remove or significantly trim the 'When to Use This Skill', 'Best Practices', and 'Common Pitfalls' sections as they explain concepts Claude already understands about testing
Consider moving detailed examples (like the full ConcurrentBoundaryTest or DateTimeBoundaryTest classes) to separate reference files, keeping only the most essential patterns inline
The Maven/Gradle setup section could be condensed since Claude knows how to add dependencies - just list the artifact names
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity like the 'When to Use This Skill' section listing obvious cases, and the 'Best Practices' and 'Common Pitfalls' sections contain information Claude would already know about testing fundamentals. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all tests are complete, copy-paste ready JUnit 5 tests with proper imports, assertions, and realistic boundary scenarios. The parameterized test examples are particularly well-structured. | 3 / 3 |
Workflow Clarity | For a skill focused on test patterns rather than multi-step processes, the organization is clear. Each section covers a distinct boundary testing domain with complete, self-contained examples. No destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-organized into logical sections, but the skill is quite long (300+ lines) and could benefit from splitting detailed examples into separate reference files. The References section at the end is good, but inline content could be trimmed with links to expanded examples. | 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.