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 articulates specific capabilities (tool handlers, resources, prompt templates, transports), includes an explicit 'Use when' clause with relevant trigger terms, and occupies a distinct niche at the intersection of Spring Boot, MCP, and Spring AI. The description is well-structured, uses third person voice, and provides enough detail for accurate skill selection.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'defining tool handlers', 'exposing resources', 'configuring prompt templates', 'setting up transports for AI function calling and tool calling'. These are concrete, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (provides Spring Boot MCP server patterns with specific capabilities listed) and 'when' (explicit 'Use when building MCP servers...implementing AI tools, custom function calling, or MCP client integration').

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'Spring Boot', 'MCP server', 'Model Context Protocol', 'Spring AI', 'tool handlers', 'function calling', 'tool calling', 'MCP client integration'. Good coverage of both full names and common terms in this domain.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche combining Spring Boot + MCP + Spring AI. The specific technology stack (Spring Boot MCP servers with Spring AI) is narrow enough to be clearly distinguishable from generic Spring, generic MCP, or generic AI 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 well-structured skill with strong actionability and excellent progressive disclosure. The code examples are concrete and executable, and references are clearly organized. The main weaknesses are some verbosity in the best practices section (generic advice Claude already knows) and the lack of explicit validation/verification checkpoints in the multi-step workflow.

Suggestions

Add explicit validation checkpoints between workflow steps, e.g., 'Verify server starts: curl http://localhost:8080/mcp/health' after transport configuration, and 'Run tests before deploying' after the testing step.

Trim the Best Practices section to only include Spring AI MCP-specific guidance — remove generic advice like 'use @Cacheable' and 'set timeouts' that Claude already knows.

DimensionReasoningScore

Conciseness

Generally efficient but includes some unnecessary verbosity — e.g., the Best Practices section has bullet points that are somewhat generic (like 'use @Cacheable', 'set timeouts') that Claude already knows. The dependency blocks in both Maven and Gradle are slightly redundant. However, most content earns its place.

2 / 3

Actionability

Provides fully executable, copy-paste ready code examples throughout — from project setup with @EnableMcpServer, to tool definitions with @Tool/@ToolParam, prompt templates, security configuration, testing, and YAML transport config. All examples are concrete and complete.

3 / 3

Workflow Clarity

Steps are numbered (1-6) and logically sequenced, but there are no explicit validation checkpoints or feedback loops. For a multi-step server setup involving security and transport configuration, there should be verification steps (e.g., 'verify server starts', 'test tool endpoint responds') between stages.

2 / 3

Progressive Disclosure

Excellent progressive disclosure — the main file provides a clear overview with working examples, then consistently points to one-level-deep reference files (implementation-patterns.md, testing-guide.md, examples.md, api-reference.md, etc.) with clear descriptions of what each contains. Navigation is well-signaled throughout.

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