java-architect
Use when building enterprise Java applications with Spring Boot 3.x, microservices, or reactive programming. Invoke for WebFlux, JPA optimization, Spring Security, cloud-native patterns.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill java-architectOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has strong trigger term coverage and clear distinctiveness within the Spring Boot ecosystem, making it easy to identify when this skill should be selected. However, it lacks specificity about what concrete actions the skill performs - it reads more like a topic list than a capability description. The 'Use when' clause is present but would benefit from the 'what' portion being strengthened with actual actions.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Builds REST APIs, configures authentication, optimizes database queries, implements reactive streams' before the 'Use when' clause.
Transform the technology list into capability statements, e.g., 'Implements Spring Security authentication and authorization' instead of just 'Spring Security'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Spring Boot 3.x, microservices, reactive programming) and mentions specific technologies (WebFlux, JPA, Spring Security), but doesn't describe concrete actions - only lists topics without explaining what actions can be performed. | 2 / 3 |
Completeness | Has a 'Use when' clause which addresses when to use it, but the 'what' is weak - it lists technologies but doesn't explain what the skill actually does (e.g., 'builds APIs', 'configures security', 'optimizes queries'). | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Spring Boot', 'microservices', 'reactive programming', 'WebFlux', 'JPA', 'Spring Security', 'cloud-native', 'enterprise Java' - these are all terms developers naturally use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche targeting Spring Boot 3.x specifically with clear technology markers (WebFlux, JPA, Spring Security). Unlikely to conflict with generic Java or other framework skills due to specific Spring ecosystem terminology. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structural organization with a clear reference table for progressive disclosure, but critically lacks actionable content. It reads more like a role description than executable guidance - there are no code examples, specific commands, or concrete patterns despite being a technical Java/Spring Boot skill. The constraints (MUST DO/MUST NOT DO) are useful but would benefit from examples showing correct vs incorrect implementations.
Suggestions
Add executable code examples for each major topic (e.g., a complete WebFlux controller, a JPA repository with optimized query, a Spring Security configuration)
Replace vague workflow steps with specific commands and validation checkpoints (e.g., 'Run `./mvnw test` to verify 85%+ coverage before proceeding')
Remove the persona/role framing ('15+ years experience', 'Senior Java architect') - Claude doesn't need this context to perform the task
Add concrete examples in the constraints section showing what deprecated APIs to avoid and what to use instead
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary framing ('15+ years of enterprise Java experience', 'Senior Java architect') that Claude doesn't need. The constraints and knowledge reference sections are reasonably efficient, but the role definition adds little actionable value. | 2 / 3 |
Actionability | The skill provides no executable code examples, only abstract guidance like 'Build services with Spring Boot best practices' and 'Optimize JPA queries'. There are no concrete commands, code snippets, or copy-paste ready implementations despite being a technical Java skill. | 1 / 3 |
Workflow Clarity | The core workflow lists 5 steps but lacks validation checkpoints, specific commands, or feedback loops. Steps like 'Implementation - Build services with Spring Boot best practices' are too vague to guide actual execution. | 2 / 3 |
Progressive Disclosure | The reference table with clear 'Load When' conditions is well-structured. Content is appropriately split with one-level-deep references to specific topic files, and navigation is clear and well-signaled. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
- 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.