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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

The body is concise, highly actionable, and has a clear framework-detection workflow. It is held back only on progressive disclosure, since a large single-file reference could offload framework-specific detail into separate bundled files.

Suggestions

Move the more extensive Spring- or Quarkus-specific sections (e.g., reactive patterns, Panache, testing) into separate reference files and link to them from a concise overview, improving progressive disclosure.

Consider a brief 'Quick reference' summary at the top so the most common conventions are reachable without scanning all sections.

Dimension	Reasoning	Score
Conciseness	Lean PASS/FAIL code examples with minimal prose, assumes competence, and adds only framework-specific knowledge rather than basic Java explanations.	3 / 3
Actionability	Provides concrete, executable code snippets across every section with clear PASS/FAIL labels, copy-paste ready and specific to each framework.	3 / 3
Workflow Clarity	Framework Detection is a clear branching decision procedure (quarkus → QUARKUS, spring-boot → SPRING, neither → shared); as a standards-reference skill with no destructive batch operation, no validation loop is required.	3 / 3
Progressive Disclosure	Well-organized sections with [SPRING]/[QUARKUS] tags, but it is a single ~380-line monolithic file with no external references where framework-specific content could be split out.	2 / 3
	Total	11 / 12 Passed

Description

82%

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 specific, third-person, and clearly scoped to a distinct niche with strong natural trigger terms. Its main weakness is the missing explicit 'Use when...' clause, which caps completeness.

Suggestions

Append an explicit 'Use when...' clause naming the trigger situations (e.g., 'Use when writing or reviewing Java in Spring Boot or Quarkus projects') to raise completeness to 3.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities — 'naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly states what the skill does, but there is no explicit 'Use when...' trigger clause, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Natural terms a user would say are well covered: 'Java coding standards', 'Spring Boot', 'Quarkus', naming, immutability, exceptions, reactive patterns.	3 / 3
Distinctiveness Conflict Risk	Scoped to Spring Boot and Quarkus Java services with framework-specific conventions, giving it a clear niche unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Commit: 4130457

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.