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 communicates specific capabilities (stubbing, verifying, simulating failures), names the key technology (WireMock), and provides explicit trigger guidance via a 'Use when' clause. It uses proper third-person voice throughout and includes natural keywords developers would use when seeking this functionality.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: stubs API responses, verifies request details, simulates failures (timeouts, 4xx/5xx errors), validates HTTP client behavior. These are clear, actionable capabilities.

3 / 3

Completeness

Clearly answers both what ('Stubs API responses, verifies request details, simulates failures...') and when ('Use when testing service integrations with external APIs or mocking HTTP endpoints'). Explicit 'Use when' clause is present.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'unit testing', 'REST APIs', 'WireMock', 'mock HTTP endpoints', 'service integrations', 'external APIs', 'timeouts', '4xx/5xx errors'. Good coverage of terms a developer would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: WireMock-based REST API testing. The combination of WireMock, HTTP mocking, and external API testing creates a very specific domain unlikely to conflict with other 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—the complete Java example with imports and Maven dependencies is immediately usable. The progressive disclosure is well-handled with appropriate references. Minor weaknesses include some redundancy between Best Practices and Constraints sections, and the workflow could benefit from an inline error scenario example rather than deferring all advanced patterns to a reference file.

Suggestions

Merge 'Best Practices' and 'Constraints and Warnings' into a single concise section to reduce redundancy (e.g., dynamic ports is mentioned in both).

Remove or condense the 'When to Use' section—Claude can infer applicability from the overview and description.

DimensionReasoningScore

Conciseness

Generally efficient but includes some unnecessary sections like 'When to Use' (Claude can infer this) and the 'Best Practices' section has items that overlap with constraints/warnings. The bullet lists could be tighter, though the code examples are appropriately sized.

2 / 3

Actionability

Provides fully executable Java code with proper imports, a complete test class, Maven dependency declarations, and specific API calls. The basic stubbing example is copy-paste ready and demonstrates the full workflow from setup to verification.

3 / 3

Workflow Clarity

The numbered instructions provide a clear sequence, and troubleshooting tips are helpful. However, there are no explicit validation checkpoints—e.g., no guidance on what to check if stubs aren't matching beyond brief tips, and the error scenarios are deferred to a reference file rather than shown inline with at least a minimal example.

2 / 3

Progressive Disclosure

Well-structured with a concise overview, inline basic example, and clear one-level-deep reference to 'references/advanced-examples.md' for advanced topics. External documentation links are clearly signaled. Content is appropriately split between the main file and references.

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