java-coding-standards

Spring Bootサービス向けのJavaコーディング標準：命名、不変性、Optional使用、ストリーム、例外、ジェネリクス、プロジェクトレイアウト。

Quality

47%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/ja-JP/skills/java-coding-standards/SKILL.md

Quality

Discovery

32%

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 identifies its domain (Java/Spring Boot coding standards) and lists relevant topic areas, but it reads more like a table of contents than an actionable skill description. It lacks concrete actions (what does it do with these standards—enforce them? generate code following them? review code against them?) and entirely omits 'when to use' guidance, which is critical for skill selection.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when writing or reviewing Java code for Spring Boot projects, or when the user asks about Java coding conventions, naming standards, or project structure.'

Replace the category list with concrete actions, e.g., 'Enforces naming conventions, ensures immutability patterns, validates proper Optional and Stream usage, and structures Spring Boot project layouts according to team standards.'

Include natural trigger terms in both Japanese and English if the skill should serve multilingual users, and add common variations like 'code style', 'best practices', 'code review', '.java files'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Java/Spring Boot) and lists several topic areas (naming, immutability, Optional usage, streams, exceptions, generics, project layout), but these are categories rather than concrete actions. It doesn't describe what the skill actually does with these topics (e.g., 'enforces', 'validates', 'applies').	2 / 3
Completeness	The description addresses 'what' (Java coding standards for Spring Boot) at a high level but completely lacks any 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric should cap completeness at 2, and since the 'what' is also somewhat weak, a score of 1 is appropriate.	1 / 3
Trigger Term Quality	Contains relevant keywords like 'Java', 'Spring Boot', 'コーディング標準' (coding standards), 'Optional', 'ストリーム' (streams), 'ジェネリクス' (generics). However, it's in Japanese which limits natural matching for English-speaking users, and it misses common variations like 'code style', 'best practices', 'conventions', or file extensions like '.java'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Spring Boot' + 'Java' + 'coding standards' provides some specificity, but it could overlap with general Java style guides, Spring Boot project setup skills, or broader code review skills. The niche is somewhat defined but not sharply distinct.	2 / 3
	Total	7 / 12 Passed

Implementation

62%

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

This is a competent Java coding standards skill with good structure and concrete code examples in key areas. Its main weaknesses are including some knowledge Claude already possesses (standard naming conventions, basic code smells) and having incomplete examples in several sections. The content would benefit from trimming well-known conventions and completing the partial code examples.

Suggestions

Remove or significantly condense sections covering knowledge Claude already has (naming conventions like PascalCase/camelCase, standard Maven layout, basic code smells like 'avoid magic numbers').

Complete partial code examples — e.g., provide a full implementation for the generics `indexById` method and a concrete exception class definition for `MarketNotFoundException`.

Consider splitting detailed sections (testing expectations, project structure, logging patterns) into separate referenced files to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Generally efficient with good use of code examples, but includes some guidance Claude already knows (e.g., basic naming conventions like PascalCase/camelCase, standard Maven project structure, basic code smells). The 'avoid code smells' section is largely common knowledge for Claude.	2 / 3
Actionability	Provides concrete code examples for naming, immutability, Optional, streams, and logging, which is good. However, several sections (exceptions, generics, formatting, testing) give only partial guidance or abstract rules without complete executable examples. The generics example uses `{ ... }` instead of a complete implementation.	2 / 3
Workflow Clarity	This is a coding standards/style guide skill, not a multi-step workflow. For this type of single-purpose reference skill, the content is clearly organized into logical sections with unambiguous guidance. No destructive or batch operations require validation checkpoints.	3 / 3
Progressive Disclosure	Content is well-structured with clear section headers, but it's a monolithic file that could benefit from splitting detailed sections (e.g., testing expectations, project structure) into separate references. No bundle files are provided, and no external references are used despite the content being moderately long.	2 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: affaan-m/everything-claude-code
Commit: 928076c

Reviewed: 3 days 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.