java
Expert in Java development with Spring Boot and enterprise patterns
35
22%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./java/SKILL.mdQuality
Discovery
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 declarative, stating expertise rather than describing concrete capabilities. It lacks any 'Use when...' guidance, making it difficult for Claude to know when to select this skill. The description would benefit from listing specific actions (e.g., 'Creates REST APIs', 'Configures dependency injection') and explicit trigger conditions.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates REST APIs, configures Spring Security, sets up database connections with JPA/Hibernate, implements dependency injection patterns'
Add an explicit 'Use when...' clause with trigger terms like 'Spring Boot project', 'Java backend', 'REST API', 'microservices', '@Autowired', 'application.properties'
Replace 'Expert in' with third-person action verbs describing what the skill does, not what it claims to be
| 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 it actually does - no verbs indicating specific capabilities. | 1 / 3 |
Completeness | Only weakly addresses 'what' (expertise area) and completely missing 'when' - no 'Use when...' clause or explicit trigger guidance. Does not tell Claude when to select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords users might say ('Java', 'Spring Boot', 'enterprise'), but misses common variations like 'REST API', 'microservices', 'Maven', 'Gradle', '.java files', or specific Spring components users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | 'Spring Boot' provides some specificity that distinguishes from generic Java skills, but 'enterprise patterns' is vague and could overlap with many backend development skills. Could conflict with general Java or backend development skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a high-level style guide than actionable instructions. It lists many good practices but provides no concrete code examples, specific commands, or step-by-step workflows. Claude already knows most of these general principles; the skill would be more valuable with executable examples and specific patterns unique to this codebase or team.
Suggestions
Add concrete, executable code examples for key patterns (e.g., a complete controller with exception handling, a service with constructor injection, a repository query)
Include a workflow for common tasks like 'Creating a new REST endpoint' with numbered steps and validation checkpoints
Remove general programming knowledge Claude already has (SOLID principles, naming conventions, basic testing concepts) and focus on project-specific patterns or preferences
Consider splitting into separate files (SPRING_BOOT.md, QUARKUS.md, TESTING.md) with SKILL.md as a navigation overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some guidance Claude already knows (SOLID principles, naming conventions, basic testing practices). Could be tightened by removing general programming knowledge. | 2 / 3 |
Actionability | Almost entirely abstract guidance with no concrete code examples, commands, or executable snippets. Statements like 'Use constructor injection' and 'Implement proper validation' describe rather than instruct with specific implementations. | 1 / 3 |
Workflow Clarity | No workflows, sequences, or processes are defined. The content is a list of principles and recommendations without any step-by-step guidance for common tasks like setting up a project, implementing a feature, or debugging. | 1 / 3 |
Progressive Disclosure | Content is organized into logical sections with clear headers, but everything is inline with no references to detailed materials. The breadth of topics (Spring Boot, Quarkus, testing, performance) suggests some content should be split into separate files. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
68%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 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- Repository
- mindrally/skills
- Commit
47f47c1
- Reviewed
Table of Contents
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.