jbvc/java-coding-standards
Java coding standards for Spring Boot services: naming, immutability, Optional usage, streams, exceptions, generics, and project layout.
78
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
67%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 is strong in specificity and distinctiveness, clearly identifying its domain (Java/Spring Boot coding standards) and listing concrete topics it covers. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are decent but could include more natural user phrasings.
Suggestions
Add a 'Use when...' clause such as 'Use when writing or reviewing Java/Spring Boot code, or when the user asks about Java coding conventions, best practices, or code style.'
Include additional natural trigger terms like 'code style', 'best practices', 'code review', 'conventions', '.java files' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete areas: naming, immutability, Optional usage, streams, exceptions, generics, and project layout. These are concrete, well-defined coding standard topics rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers 'what' (Java coding standards covering specific topics for Spring Boot services), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes good natural keywords like 'Java', 'Spring Boot', 'naming', 'Optional', 'streams', 'exceptions', 'generics', but misses common user phrasings like 'code style', 'best practices', 'code review', 'conventions', or file extensions like '.java'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Java', 'Spring Boot', and specific coding standard topics (immutability, Optional usage, streams, generics) creates a clear niche that is unlikely to conflict with other skills. It's distinctly about Java/Spring Boot coding conventions. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%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 coding standards skill with strong actionability through concrete Java code examples and clear section organization. Its main weakness is moderate verbosity—several sections cover well-known best practices that Claude already understands (code smells, formatting basics), consuming tokens without adding unique value. The content would benefit from trimming common-knowledge advice and potentially splitting into a concise overview with references to detailed sub-files.
Suggestions
Remove or significantly trim sections covering common knowledge Claude already has (Code Smells to Avoid, Formatting and Style basics) to improve token efficiency.
Consider splitting detailed sections (project structure, testing expectations, logging) into separate referenced files, keeping SKILL.md as a concise overview with links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of code examples, but some sections state things Claude already knows (e.g., 'Prefer clarity over cleverness', 'Keep methods short and focused', code smells like 'deep nesting → early returns'). The 'Code Smells to Avoid' and 'Formatting and Style' sections are largely common knowledge for an LLM trained on vast Java codebases. | 2 / 3 |
Actionability | Provides concrete, executable Java code examples for nearly every convention (naming, immutability, Optional, streams, logging, generics). The examples are copy-paste ready and specific to Spring Boot contexts, making it clear exactly what patterns to follow. | 3 / 3 |
Workflow Clarity | This is a coding standards skill, not a multi-step workflow skill. The single-purpose nature (apply these conventions when writing Java) is unambiguous, and each section clearly delineates when and how to apply each standard. No destructive or batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but it's a fairly long monolithic document. Some sections like project structure, testing expectations, and code smells could be split into referenced files. No external references are provided for deeper dives on any topic. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%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.
Reviewed
Table of Contents