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 a narrow, well-scoped domain (testing Spring scheduled and async methods), lists specific concrete capabilities, names the relevant technologies, and includes an explicit 'Use when' clause with natural trigger terms. It serves as a strong example of a well-crafted skill description.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: mocking task execution and timing, verifying execution counts, testing cron expressions, validating retry behavior, and simulating thread pool behavior. Also names specific technologies (JUnit 5, CompletableFuture, Awaitility, Mockito).

3 / 3

Completeness

Clearly answers both 'what' (patterns for unit testing Spring @Scheduled and @Async methods with specific tools and techniques) and 'when' (explicit 'Use when testing background tasks, cron jobs, periodic execution, scheduled tasks, or thread pool behavior').

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'unit testing', '@Scheduled', '@Async', 'background tasks', 'cron jobs', 'periodic execution', 'scheduled tasks', 'thread pool behavior', plus specific library names like 'Awaitility' and 'Mockito' that users would mention.

3 / 3

Distinctiveness Conflict Risk

Highly specific niche: Spring scheduled/async method testing with named frameworks. Unlikely to conflict with general testing skills or general Spring skills due to the narrow focus on @Scheduled/@Async testing patterns.

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 concrete Java examples and good progressive disclosure to reference files. Its main weakness is moderate redundancy across the Best Practices, Common Pitfalls, and Constraints sections, which repeat similar points about calling methods directly, setting timeouts, and mocking dependencies. Tightening these overlapping sections would improve token efficiency.

Suggestions

Merge 'Best Practices', 'Common Pitfalls', and 'Constraints and Warnings' into a single concise section (e.g., 'Key Rules') to eliminate repeated guidance about direct method calls, timeouts, and mocking.

Remove or significantly trim the 'When to Use' section — it restates the overview and description without adding new information.

DimensionReasoningScore

Conciseness

The content is mostly efficient but includes some redundancy — the 'When to Use' section largely restates the overview, and 'Common Pitfalls' and 'Constraints and Warnings' overlap significantly (e.g., self-invocation, timeout warnings, calling methods directly). The 'Best Practices' section also repeats points from Instructions. Claude already knows what @Async and @Scheduled do.

2 / 3

Actionability

The examples are concrete, executable Java code with real annotations, assertions, and library usage. The instructions give specific, copy-paste-ready patterns for CompletableFuture.get(), Awaitility.await(), and exception handling with clear method calls and assertions.

3 / 3

Workflow Clarity

The Instructions section provides a numbered sequence with validation checkpoints, which is good. However, the validation checkpoints are more like troubleshooting tips than true feedback loops — there's no explicit 'if test fails, do X, then re-run' cycle. For a testing skill, the workflow is adequate but the checkpoints could be more structured.

2 / 3

Progressive Disclosure

The skill provides a clear overview with inline key patterns and appropriately defers full examples, dependencies, and additional test classes to 'references/examples.md'. References are one level deep and clearly signaled throughout the document.

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