java

Expert in Java development with Spring Boot and enterprise patterns

Quality

14%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./java/SKILL.md

Quality

Content

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads as a generic checklist of Java/Spring Boot best practices that Claude already knows, providing no concrete code examples, no executable guidance, and no novel information. It violates the core principle that skills should add only what Claude doesn't already know. The content would need a complete rewrite focused on project-specific conventions, concrete code patterns, or executable workflows to be useful.

Suggestions

Replace abstract bullets with concrete, executable code examples — e.g., show the exact exception handler pattern, the constructor injection pattern, or a sample controller/service/repository structure with actual Java code.

Remove all guidance that restates common Java knowledge (SOLID, naming conventions, 'write clean code') and focus only on project-specific conventions or non-obvious patterns Claude wouldn't already know.

Add at least one multi-step workflow with validation — e.g., steps to scaffold a new Spring Boot service, create an endpoint, write tests, and verify the build passes.

Either add bundle files with detailed reference material (e.g., project-specific configuration templates, error response schemas) and link to them, or provide concrete inline examples that are copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The content is largely a list of things Claude already knows — SOLID principles, naming conventions, Spring Boot best practices, layered architecture, JUnit testing, connection pooling, etc. Almost every bullet point restates common Java knowledge without adding anything Claude wouldn't already know. Very little earns its token cost.	1 / 3
Actionability	There are zero code examples, zero executable commands, and zero concrete patterns. Every bullet is abstract guidance like 'Use constructor injection over field injection' or 'Implement caching strategies' without showing how. This describes rather than instructs.	1 / 3
Workflow Clarity	There are no multi-step workflows, no sequenced processes, and no validation checkpoints. The content is an unordered collection of general advice with no clear workflow for any task.	1 / 3
Progressive Disclosure	The content is organized into logical sections with clear headers, which provides some structure. However, there are no references to external files, no bundle files, and the content is a flat list of bullet points that could benefit from deeper reference materials for specific topics like Spring Security configuration or Quarkus native builds.	2 / 3
	Total	5 / 12 Passed

Description

22%

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 description is too vague and reads more like a resume headline than a functional skill description. It lacks concrete actions, explicit trigger conditions, and sufficient detail for Claude to reliably select it from a pool of skills. The use of 'Expert in' is fluff that doesn't convey what the skill actually does.

Suggestions

Replace 'Expert in Java development' with specific concrete actions, e.g., 'Creates Spring Boot applications, configures REST APIs, implements dependency injection, sets up database connections with JPA/Hibernate.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Java projects, Spring Boot configuration, Maven/Gradle builds, REST endpoints, or enterprise Java patterns.'

Remove the vague 'Expert in' phrasing and use third-person active voice describing capabilities (e.g., 'Develops', 'Configures', 'Debugs').

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Expert in' without listing any concrete actions. It names a domain (Java/Spring Boot) but doesn't describe what the skill actually does—no verbs like 'creates', 'configures', 'debugs', etc.	1 / 3
Completeness	The description weakly addresses 'what' (Java development) but provides no 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent, and the 'what' itself is too vague to be useful.	1 / 3
Trigger Term Quality	It includes some relevant keywords ('Java', 'Spring Boot', 'enterprise patterns') that users might mention, but misses common variations and specific terms like 'REST API', 'microservices', 'dependency injection', 'Maven', 'Gradle', '.java files', etc.	2 / 3
Distinctiveness Conflict Risk	While 'Spring Boot' adds some specificity, 'Java development' and 'enterprise patterns' are broad enough to overlap with general coding skills, backend development skills, or other Java-related skills.	2 / 3
	Total	6 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: mindrally/skills
Commit: 05a7130

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.