Unit tests for JSON serialization/deserialization with Jackson and @JsonTest. Use when validating JSON mapping, custom serializers, and date format handling.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill unit-test-json-serialization81
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
100%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 follows best practices. It uses third person voice, specifies concrete capabilities (Jackson, @JsonTest, serialization/deserialization), and includes an explicit 'Use when...' clause with relevant trigger scenarios. The description is concise yet comprehensive enough to distinguish it from general testing or JSON processing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'JSON serialization/deserialization with Jackson', '@JsonTest', 'validating JSON mapping', 'custom serializers', and 'date format handling'. | 3 / 3 |
Completeness | Clearly answers both what ('Unit tests for JSON serialization/deserialization with Jackson and @JsonTest') and when ('Use when validating JSON mapping, custom serializers, and date format handling') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'unit tests', 'JSON', 'serialization', 'deserialization', 'Jackson', '@JsonTest', 'JSON mapping', 'serializers', 'date format'. Good coverage of technical terms users working with Spring Boot JSON testing would use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting Jackson-based JSON testing specifically with @JsonTest annotation. The combination of Jackson, @JsonTest, and specific use cases (custom serializers, date format handling) creates a distinct trigger profile unlikely to conflict with general testing or other JSON skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable code examples for JSON testing with @JsonTest that are immediately usable. However, it's verbose with unnecessary explanatory sections and could benefit from better organization through progressive disclosure. The workflow guidance lacks explicit validation steps and error recovery patterns.
Suggestions
Remove the 'When to Use This Skill' section - these use cases are self-evident from the skill title and description
Add a troubleshooting workflow with specific steps: run test -> examine assertion failure -> check Jackson annotations -> verify JSON structure -> re-run
Move advanced topics (polymorphic deserialization, custom serializers) to separate reference files and link to them from a condensed overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'When to Use This Skill' that explains obvious use cases Claude would infer. The Maven/Gradle setup is standard boilerplate that could be trimmed. However, the code examples themselves are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout. Each pattern includes complete test methods with proper imports, annotations, and assertions that can be directly used. | 3 / 3 |
Workflow Clarity | The skill presents patterns clearly but lacks explicit validation checkpoints or feedback loops. For JSON testing, there's no guidance on what to do when tests fail or how to debug serialization mismatches. The troubleshooting section is minimal. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear section headers, but it's a monolithic document with no references to external files for advanced topics. The polymorphic and custom serializer sections could be split into separate reference files. | 2 / 3 |
Total | 9 / 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 | |
Table of Contents
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.