tdg-personal/java-coding-standards
"Java coding standards for Spring Boot services: naming, immutability, Optional usage, streams, exceptions, generics, and project layout."
73
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
42%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 does a good job listing specific coding standard topics, making it clear what areas it covers. However, it critically lacks any 'Use when...' guidance, which would help Claude know when to select this skill over other Java or coding-related skills. Adding explicit trigger conditions and a few more natural user terms would significantly improve its effectiveness.
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, code style, or best practices.'
Include additional natural trigger terms users might say, such as 'code style', 'best practices', 'code review', 'Java conventions', or 'Spring Boot standards'.
Consider adding scope boundaries like 'Does not cover Spring Boot configuration or deployment' to further reduce conflict risk with related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete areas: naming, immutability, Optional usage, streams, exceptions, generics, and project layout. These are concrete, recognizable coding standard topics rather than vague abstractions. | 3 / 3 |
Completeness | Describes what the skill covers (Java coding standards for various topics) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores at 1. | 1 / 3 |
Trigger Term Quality | Includes good natural keywords like 'Java', 'Spring Boot', 'naming', 'Optional', 'streams', 'exceptions', 'generics', and 'project layout'. However, it misses common user variations like 'code style', 'best practices', 'code review', 'conventions', or file extensions like '.java'. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Spring Boot services' and listing specific topics like 'Optional usage' and 'immutability' provides some distinctiveness, but it could overlap with general Java coding skills, Spring Boot development skills, or generic code review/style skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong coding standards skill that is concise, well-structured, and highly actionable with concrete Java code examples throughout. It correctly assumes Claude's competence and avoids explaining basic concepts. The only minor weakness is the lack of progressive disclosure via external references, though the content length is manageable enough that this is a minor concern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Java, Spring Boot, or basic concepts are. Every section delivers concrete conventions without padding. The PASS/FAIL annotations are a compact way to communicate expectations. | 3 / 3 |
Actionability | Nearly every section includes concrete, executable Java code examples demonstrating the correct pattern. Naming, immutability, Optional, streams, logging, and generics all have copy-paste-ready code. The few sections without code (e.g., Code Smells) provide specific, actionable rules rather than vague guidance. | 3 / 3 |
Workflow Clarity | This is a coding standards skill, not a multi-step workflow skill. The single-purpose nature (enforce conventions) is unambiguous, and the 'When to Activate' section clearly defines when to apply these standards. No destructive or batch operations are involved, so validation checkpoints are not needed. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but it's entirely self-contained with no references to external files for deeper dives. Some sections like Testing Expectations or Project Structure could benefit from linking to more detailed guides. However, the content length is reasonable and doesn't feel like a monolithic wall. | 2 / 3 |
Total | 11 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents