Name: java-coding-standards
Rating: 59.2 (1 reviews)
Author: affaan-m

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

69%

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

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/java-coding-standards/SKILL.md

The canonical home for this skill is java-coding-standards in affaan-m/ECC

Quality

Content

72%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.

The content is highly actionable and concise, with executable PASS/FAIL examples across all major topics, but it functions as a single long reference catalog with limited workflow sequencing and no progressive disclosure into separate files.

Suggestions

Add a short review workflow with validation checkpoints (e.g. detect framework → apply conventions → verify naming/immutability/exception checks pass) to lift workflow clarity above a reference catalog.

Split the largest sections (Reactive Patterns, Testing Expectations, Project Structure) into one-level-deep reference files linked from SKILL.md to improve navigation and reduce inline bulk.

Replace the few partial snippets (e.g. `indexById(...) { ... }`) with complete executable bodies or explicitly mark them as signatures to keep actionability consistent throughout.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's Java competence — mostly PASS/FAIL code snippets and short bullets without explaining what records, Optional, or CDI are — with only minor trimmable commentary such as the Panache accessor note.	4 / 5
Actionability	Provides copy-paste-ready executable patterns across naming, immutability, DI, reactive pipelines, exceptions, generics, layout, logging, config, and tests, with explicit PASS/FAIL labels covering the common cases.	5 / 5
Workflow Clarity	The Framework Detection steps (build file contains quarkus/spring-boot → apply conventions) give a basic sequence, but the body is primarily a reference catalog with no validation checkpoints or feedback loops for the review/apply workflow.	3 / 5
Progressive Disclosure	Section headers are clear, but the ~380-line body is monolithic with no bundle files or one-level-deep references; several large reference blocks (reactive patterns, testing, project structure) could be split into separate files for easier navigation.	3 / 5
	Total	15 / 20 Passed

Description

66%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.

The description is specific and well-targeted to a clear Spring Boot/Quarkus Java niche with strong trigger terms, but it lacks an explicit "Use when..." trigger clause, leaving the "when" dimension only weakly implied.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when writing or reviewing Java code in Spring Boot or Quarkus services, or when the user mentions naming, immutability, Optional, streams, or CDI conventions.'

Include a few natural synonyms/file cues (e.g. '.java', 'records', 'sealed classes', 'Panache') to broaden trigger coverage.

Tighten the trailing 'Automatically applies framework-specific conventions' into a concrete trigger phrase so the 'when' is explicit rather than implied.

Dimension	Reasoning	Score
Specificity	Names the domain (Java for Spring Boot/Quarkus) and lists several concrete areas — "naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout" — giving broad coverage, though these are topic categories rather than discrete actions.	4 / 5
Completeness	The "what" is clear and detailed, but there is no "Use when..." clause or equivalent explicit trigger guidance — only the weakly implied "Automatically applies framework-specific conventions" — so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Contains natural terms a user would say ("Java coding standards", "Spring Boot", "Quarkus", "Optional", "streams", "CDI", "reactive patterns") with good keyword coverage, but is missing a few common synonyms and explicit file/extension cues.	4 / 5
Distinctiveness Conflict Risk	The Spring Boot + Quarkus Java niche is mostly distinct with clear triggers, with only minor overlap risk against generic Java standards skills.	4 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

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

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.