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 a strong skill description that clearly defines its scope (Mockito-based service layer unit testing), lists specific concrete actions, and includes an explicit 'Use when' clause with natural trigger terms. It uses proper third-person voice throughout and is concise without being vague. The description would effectively differentiate this skill from related testing skills (e.g., integration tests, controller tests, repository tests).

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'mock repository calls', 'verify method invocations', 'test exception scenarios', 'stub external API responses'. These are clear, actionable capabilities.

3 / 3

Completeness

Clearly answers both what ('Creates isolated tests that mock repository calls, verify method invocations, test exception scenarios, and stub external API responses') and when ('Use when testing service behaviors and business logic without database or external services').

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'unit testing', 'service layer', 'Mockito', 'mock', 'repository', 'stub', 'exception scenarios', 'business logic'. These cover common terms developers use when seeking this kind of help.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: Mockito-based service layer unit testing. The combination of 'Mockito', 'service layer', and 'mock repository calls' makes it unlikely to conflict with integration testing, controller testing, or other test-related 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 skill with excellent actionability through complete, executable Java code examples and good progressive disclosure. Its main weaknesses are moderate verbosity in the overview/when-to-use/best-practices sections that repeat known concepts, and workflow validation checkpoints that are more aspirational than concrete. The constraints section mixes genuinely useful Mockito-specific gotchas (argument matcher mixing rule) with generic testing advice Claude already knows.

Suggestions

Remove or significantly trim the 'When to Use' section and 'Overview' since they largely duplicate each other and state obvious information given the skill title.

Make validation checkpoints concrete—e.g., replace 'confirm green bar' with specific commands like `mvn test -Dtest=UserServiceTest` and expected output patterns.

Trim 'Best Practices' and 'Constraints' to only Mockito-specific gotchas Claude wouldn't already know (e.g., argument matcher mixing rule, avoid @Spy), removing generic testing advice like 'tests must be independent'.

DimensionReasoningScore

Conciseness

The 'When to Use' section and 'Overview' largely repeat each other and restate what's obvious from the title. The 'Best Practices' and 'Constraints and Warnings' sections contain some advice Claude already knows (e.g., 'tests must be independent', 'test one behavior per test method'). However, the code examples are lean and the overall structure isn't excessively padded.

2 / 3

Actionability

The code examples are fully executable, copy-paste ready Java with proper annotations, imports implied by context, and clear Arrange-Act-Assert structure. Both the basic pattern and the verification pattern are concrete and complete enough to directly use.

3 / 3

Workflow Clarity

The workflow steps (1-5) are listed with some validation checkpoints ('confirm green bar', 'verify exception type and message'), but these checkpoints are vague rather than concrete commands or assertions. The steps describe a general process rather than a precise sequence with explicit feedback loops for error recovery.

2 / 3

Progressive Disclosure

The skill provides a clear overview with concise inline examples and appropriately references `references/examples.md` for advanced patterns (argument captors, async services, InOrder). External documentation links are well-signaled. Content is well-organized with logical sections.

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