CtrlK
BlogDocsLog inGet started
Tessl Logo

giuseppe-trisciuoglio/developer-kit

Comprehensive developer toolkit providing reusable skills for Java/Spring Boot, TypeScript/NestJS/React/Next.js, Python, PHP, AWS CloudFormation, AI/RAG, DevOps, and more.

89

Quality

89%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

Overview
Quality
Evals
Security
Files

Quality

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 an excellent skill description that is specific, well-scoped, and includes strong trigger terms. It clearly communicates both what the skill does (generates various types of bean validation tests) and when to use it (explicit 'Use when...' clause). The mention of specific annotations, Hibernate Validator, and the distinction from Spring context testing make it highly distinctive.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: testing @Valid, @NotNull, @Min, @Max, @Email constraints, generating custom validator tests, constraint violation assertions, validation groups, and parameterized validation tests. Very detailed and actionable.

3 / 3

Completeness

Clearly answers 'what' (provides patterns for unit testing Jakarta Bean Validation with specific annotations and test types) and 'when' with an explicit 'Use when...' clause covering validation tests, bean validation tests, and custom constraint validators.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'unit testing', 'Bean Validation', 'JSR-380', '@Valid', '@NotNull', '@Min', '@Max', '@Email', 'Hibernate Validator', 'custom validator tests', 'constraint violation', 'validation groups', 'validation tests'. Good coverage of both annotation names and conceptual terms.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: Jakarta Bean Validation / JSR-380 testing with Hibernate Validator, explicitly scoped outside Spring context. The specific annotation names and 'bean validation' terminology make it unlikely to conflict with general testing or Spring-based validation skills.

3 / 3

Total

12

/

12

Passed

Implementation

72%

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 and good progressive disclosure to reference files. Its main weaknesses are moderate verbosity — overlapping sections (Best Practices, Common Pitfalls, Constraints and Warnings) that could be consolidated — and a workflow that lacks explicit validation/feedback checkpoints. The core testing patterns are well-demonstrated and immediately usable.

Suggestions

Consolidate 'Best Practices', 'Common Pitfalls', and 'Constraints and Warnings' into a single concise section to reduce redundancy and token usage.

Remove the 'When to Use' section — this information belongs in YAML frontmatter metadata, not the skill body.

DimensionReasoningScore

Conciseness

The skill includes some unnecessary sections like 'Common Pitfalls' and 'Constraints and Warnings' that overlap significantly, and the 'Best Practices' section contains advice Claude already knows (e.g., 'test edge cases', 'use clear messages'). The 'When to Use' section is also somewhat redundant with the overview. However, the code examples are lean and well-targeted.

2 / 3

Actionability

The skill provides fully executable Java code examples including Maven dependencies, base test class setup, and multiple concrete test methods with AssertJ assertions. The code is copy-paste ready and covers valid/invalid cases, property path extraction, and multiple violation testing.

3 / 3

Workflow Clarity

The numbered instructions in step 1-8 provide a reasonable sequence, but there are no explicit validation checkpoints or feedback loops. For a testing skill, there's no guidance on what to do when tests fail unexpectedly or how to debug constraint violations systematically — the troubleshooting section is separate and disconnected from the workflow.

2 / 3

Progressive Disclosure

The skill provides a clear overview with core patterns inline and appropriately delegates advanced topics (custom validators, validation groups, parameterized tests) to one-level-deep reference files. Navigation is well-signaled with descriptive bullet points for each reference file's contents.

3 / 3

Total

10

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

10

/

11

Passed

Reviewed

Table of Contents