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 completely omits 'when to use' guidance, making it difficult for Claude to reliably select this skill from a large pool.

Suggestions

Add a 'Use when...' clause specifying triggers, e.g., 'Use when writing or reviewing Java code for Spring Boot projects, or when the user asks about Java coding conventions, code style, or best practices.'

Replace the topic list with concrete actions, e.g., 'Enforces naming conventions, promotes immutability patterns, guides proper Optional and Stream API usage, and defines project layout structure for Spring Boot services.'

Include both Japanese and English trigger terms to improve matching, e.g., 'coding standards', 'コーディング規約', 'code review', 'コードレビュー'.

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) 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 (listing topics rather than actions), this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Java', 'Spring Boot', 'コーディング標準' (coding standards), 'Optional', 'ストリーム' (streams), 'ジェネリクス' (generics). However, it misses common variations users might say such as 'code style', 'best practices', 'conventions', 'code review', and English equivalents of the Japanese terms.	2 / 3
Distinctiveness Conflict Risk	The combination of Java + Spring Boot + coding standards is fairly specific and narrows the domain, but it could overlap with general Java coding skills, Spring Boot development skills, or code review skills. The lack of explicit trigger conditions increases conflict risk.	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 coding standards skill with clear structure and useful Java code examples for Spring Boot conventions. Its main weaknesses are including some knowledge Claude already possesses (standard naming conventions, common code smells) and having incomplete code examples in several sections. The content would benefit from trimming well-known conventions and completing the code snippets.

Suggestions

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

Complete the generics example (`indexById` method body) and add a concrete test example with JUnit 5 + AssertJ to make those sections fully actionable.

Consider splitting detailed sections (testing patterns, project structure, code smells) into separate reference files to improve progressive disclosure and keep the main SKILL.md focused on the most impactful conventions.

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 project structure, 'avoid magic numbers'). The 'code smells' section and some formatting rules are common knowledge for Claude.	2 / 3
Actionability	Provides concrete code examples for naming, immutability, Optional, streams, and logging, which is good. However, several sections are directive without executable examples (generics shows a signature with '...', exception section is mostly prose, test section has no code). Mixed between actionable code and abstract guidance.	2 / 3
Workflow Clarity	This is a coding standards skill (not a multi-step workflow), so there's no need for sequential validation checkpoints. The single-purpose nature of the skill—defining conventions—is clearly organized with unambiguous sections covering each concern.	3 / 3
Progressive Disclosure	Content is reasonably well-organized with clear section headers, but everything is in a single monolithic file with no references to supporting documents. Some sections (like project structure, testing expectations, code smells) could be split into separate reference files to keep the main skill leaner.	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: 841beea

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