unit-test-config-properties
Unit tests for @ConfigurationProperties classes with @ConfigurationPropertiesTest. Use when validating application configuration binding and validation.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill unit-test-config-properties79
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
75%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 reasonably well-crafted description that clearly identifies its niche in Spring Boot configuration testing. It has good completeness with explicit 'Use when' guidance and is distinctive enough to avoid conflicts. However, it could benefit from more specific actions and broader trigger term coverage to help users who may not know the exact annotation names.
Suggestions
Add more concrete actions like 'create tests for property binding, validate @Validated constraints, test nested configuration objects'
Include common user variations like 'Spring Boot configuration', 'config properties', 'application.yml binding', 'property validation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (unit tests for @ConfigurationProperties classes) and mentions a specific annotation (@ConfigurationPropertiesTest), but doesn't list multiple concrete actions like 'create tests', 'validate binding', 'test validation constraints'. | 2 / 3 |
Completeness | Clearly answers both what (unit tests for @ConfigurationProperties classes with @ConfigurationPropertiesTest) and when (validating application configuration binding and validation) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like '@ConfigurationProperties', '@ConfigurationPropertiesTest', 'configuration binding', and 'validation', but missing common variations users might say like 'config properties', 'property binding', 'Spring Boot configuration', or 'YAML binding'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Spring Boot's @ConfigurationProperties testing specifically, with distinct triggers (@ConfigurationPropertiesTest annotation) that are unlikely to conflict with general testing or configuration skills. | 3 / 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, highly actionable skill with excellent executable code examples covering the full range of ConfigurationProperties testing scenarios. The main weaknesses are moderate verbosity (explanatory sections that don't add value for Claude) and a 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', 'Best Practices', and 'Common Pitfalls' sections - these contain information Claude already knows
Consider splitting advanced patterns (type conversion, profile testing, validation) into a separate ADVANCED.md file with clear links from the main skill
Consolidate the Maven and Gradle setup into a single code block or move to a separate SETUP.md to reduce initial content length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'When to Use This Skill' that largely restates the description, and the 'Best Practices' and 'Common Pitfalls' sections contain generic advice Claude would already know. The code examples are good but could be more condensed. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready code examples throughout. Each pattern includes complete Java classes with proper imports, annotations, and test methods that can be directly used. | 3 / 3 |
Workflow Clarity | For a testing skill, the workflow is clear: setup dependencies, create properties class, write tests using ApplicationContextRunner pattern. Each test pattern is self-contained and the progression from simple to complex (basic binding → nested → validation → profiles → type conversion) is logical. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but it's a long monolithic document (~400 lines) that could benefit from splitting advanced patterns (type conversion, profile testing) into separate reference files. The References section at the end is good but inline content is heavy. | 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.