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 clearly defines its scope around JUnit 5 parameterized testing, lists specific annotations and capabilities, and includes an explicit 'Use when' clause with natural trigger terms. It is highly distinctive and would be easy for Claude to select appropriately from a large pool of skills. The description is concise yet comprehensive, avoiding vague language and unnecessary padding.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: parameterized testing patterns with JUnit 5, data-driven unit tests, and names specific annotations (@ParameterizedTest, @ValueSource, @CsvSource, @MethodSource). Also describes the concrete outcome: 'tests that run the same logic with multiple input values.'

3 / 3

Completeness

Clearly answers both 'what' (provides parameterized testing patterns, generates data-driven unit tests using specific annotations) and 'when' with an explicit 'Use when' clause covering data-driven Java tests, multiple test cases from single method, and boundary value analysis.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'parameterized testing', 'JUnit 5', 'data-driven', 'unit tests', '@ParameterizedTest', '@ValueSource', '@CsvSource', '@MethodSource', 'boundary value analysis', 'Java tests', 'multiple test cases'. These cover both annotation-specific and conceptual search terms.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: JUnit 5 parameterized testing specifically. The annotation names (@ParameterizedTest, @ValueSource, @CsvSource, @MethodSource) and the focus on data-driven/boundary value testing make it very unlikely to conflict with general Java testing or other testing 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 is a solid, highly actionable skill with excellent executable code examples covering all major JUnit 5 parameterized test annotations. Its main weaknesses are verbosity — the overview, 'When to Use', and 'Best Practices' sections contain information Claude already knows — and the monolithic structure that puts all examples inline rather than using progressive disclosure. The workflow guidance is adequate but somewhat generic for what is essentially a pattern-reference skill.

Suggestions

Remove or drastically shorten the 'Overview', 'When to Use', and 'Best Practices' sections — Claude already knows when to use parameterized tests and general testing best practices.

Move the detailed examples (everything after @ValueSource and @CsvSource basics) into a separate EXAMPLES.md file, keeping only the two most common patterns inline.

Add a concise decision table (e.g., 'simple primitives → @ValueSource | input+expected → @CsvSource | complex objects → @MethodSource') instead of the prose instructions.

DimensionReasoningScore

Conciseness

The overview and 'When to Use' sections restate information Claude already knows. The examples are well-chosen but somewhat extensive — the skill could be tightened by removing the overview paragraph and trimming obvious test cases. The 'Best Practices' section contains advice Claude would already follow.

2 / 3

Actionability

All code examples are fully executable with proper imports, concrete assertions, and realistic test scenarios. Dependency setup is provided for both Maven and Gradle. Every annotation type has a complete, copy-paste-ready example.

3 / 3

Workflow Clarity

The Instructions section provides a reasonable 5-step sequence including validation ('Run ./gradlew test --info'), but this is a pattern/reference skill rather than a multi-step destructive workflow. The steps are somewhat generic ('Choose source', 'Match parameters') rather than providing decision-tree clarity for when to use which approach.

2 / 3

Progressive Disclosure

Content is well-structured with clear headings and sections, but everything is inline in a single file. The extensive examples (7+ code blocks) could benefit from being split into a separate EXAMPLES.md or PATTERNS.md, with the main skill providing a concise quick-start and references to detailed patterns.

2 / 3

Total

9

/

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