java-coding-standards

Java coding standards for Spring Boot and Quarkus services: naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout. Automatically applies framework-specific conventions. Use when writing or reviewing Java in a Spring Boot or Quarkus service.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

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

A well-organized, highly actionable reference: nearly every section gives concrete PASS/FAIL code that covers the common Spring Boot and Quarkus cases, with a clear framework-detection procedure up front. The main improvement opportunities are trimming the few generic principle statements and splitting the large per-framework sections into separate reference files.

Suggestions

Remove generic advice lines that Claude already knows (e.g., "Prefer clarity over cleverness", "Keep methods short and focused; extract helpers", and the closing "**Remember**" paragraph) — they add tokens without adding skill-specific value (conciseness).

Consider splitting the framework-specific material into one-level-deep reference files (e.g., references/quarkus.md for Panache, reactive, Dev Services, and @ConfigMapping detail; references/spring.md for slice tests and @ConfigurationProperties), keeping SKILL.md as the shared-core overview (progressive_disclosure).

Dimension	Reasoning	Score
Conciseness	The body is dense, reference-style PASS/FAIL code with almost no padding — no tutorials on concepts Claude already knows. It is not a 5 because of a few generic lines ("Prefer clarity over cleverness", the closing "Remember: Keep code intentional, typed, and observable") that add little, and not a 3 because there is no unnecessary explanation anywhere else.	4 / 5
Actionability	Concrete, copy-paste-ready Java examples cover the common cases: PASS/FAIL annotated snippets for naming, records/Panache entities, Optional mapping, constructor vs field injection, Uni/Multi pipelines (including the double-subscribe failure), exception mappers, @ConfigMapping, and @QuarkusTest/@InjectMock tests. Only one elided body (`{ ... }` in the generics example) keeps this from being perfectly literal, but the guidance is fully executable in spirit and practice.	5 / 5
Workflow Clarity	The Framework Detection section gives a clear, unambiguous conditional procedure ("Build file contains `quarkus` → apply [QUARKUS] conventions") that sequences how to apply the standards. It is not a 5 because there are no explicit validation checkpoints or feedback loops, and not a 3 because the detection sequence is explicit and applying conventions is neither destructive nor a batch operation requiring the validation cap.	4 / 5
Progressive Disclosure	A single, well-sectioned file with consistent headers and [SPRING]/[QUARKUS] tags throughout; every section is discoverable and nothing is buried. It is not a 5 because at ~380 lines the framework-specific material (Quarkus Panache/reactive/Dev Services vs Spring slices) could be split into one-level-deep reference files, and not a 3 because the structure is good and consistently organized.	4 / 5
	Total	17 / 20 Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly answers what the skill does and when to use it, with comprehensive natural trigger terms and a clearly defined Spring Boot/Quarkus niche. The only weakness is that capabilities are listed as topics rather than actions, and minor overlap risk with generic Java standards skills.

Dimension	Reasoning	Score
Specificity	The description enumerates concrete coverage areas — "naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout" — plus a concrete behavior ("Automatically applies framework-specific conventions"). It is not a 5 because the capabilities are listed as noun topics rather than specific actions, and not a 3 because coverage is comprehensive rather than limited to 1-2 actions.	4 / 5
Completeness	Both "what" and "when" are explicitly answered: what = "Java coding standards for Spring Boot and Quarkus services" with a full topic list, and when = "Use when writing or reviewing Java in a Spring Boot or Quarkus service" — a concrete, explicit trigger phrase matching the anchor-5 example.	5 / 5
Trigger Term Quality	Natural trigger phrases users would actually say are comprehensively covered: "Java", "Spring Boot", "Quarkus", "writing or reviewing Java", and "Spring Boot or Quarkus service". These are exactly the words a developer uses when requesting this kind of help; no jargon-only or generic terms.	5 / 5
Distinctiveness Conflict Risk	The niche is clear — framework-specific Java standards for exactly two named frameworks — with mostly distinct triggers. It is not a 5 because "writing or reviewing Java" leaves minor overlap risk with a generic Java style or Spring-only standards skill.	4 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/java-coding-standards/SKILL.md
Commit: c70874f

Reviewed: 1 day 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.