java-coding-standards
Spring Bootサービス向けのJavaコーディング標準：命名、不変性、Optional使用、ストリーム、例外、ジェネリクス、プロジェクトレイアウト。
Install with Tessl CLI
npx tessl i github:affaan-m/everything-claude-code --skill java-coding-standards78
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 (Spring Boot Java coding standards) and lists relevant topic areas, but lacks concrete action verbs and completely omits guidance on when Claude should use this skill. The Japanese-only format may also limit discoverability for users who search in English.
Suggestions
Add an explicit 'Use when...' clause specifying triggers like 'when reviewing Java code', 'when asking about Spring Boot best practices', or 'when writing new Spring services'
Convert topic categories into concrete actions (e.g., 'Enforces naming conventions, validates Optional usage patterns, reviews exception handling')
Include common English trigger terms alongside Japanese to improve discoverability (e.g., 'Java coding standards', 'Spring Boot best practices', 'code style')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Spring Boot/Java) and lists several topic areas (命名/naming, 不変性/immutability, Optional使用/Optional usage, ストリーム/streams, 例外/exceptions, ジェネリクス/generics, プロジェクトレイアウト/project layout), but these are categories rather than concrete actions like 'enforce naming conventions' or 'validate exception handling patterns'. | 2 / 3 |
Completeness | Describes what the skill covers (Java coding standards for Spring Boot) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. The 'when' component is entirely missing. | 1 / 3 |
Trigger Term Quality | Contains relevant technical keywords like 'Spring Boot', 'Java', 'コーディング標準' (coding standards), 'Optional', 'ストリーム' (streams), but missing common user phrases like 'code review', 'best practices', 'style guide', or English equivalents that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The Spring Boot + Java combination provides some specificity, but 'コーディング標準' (coding standards) is broad and could overlap with other Java style guides, general code review skills, or Spring-specific skills that aren't about coding standards. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent coding standards skill that exemplifies concise, actionable guidance. It provides concrete Java code examples for each pattern, uses clear visual markers (✅/❌) for good/bad practices, and organizes content into logical sections. The skill respects Claude's intelligence by avoiding explanations of basic concepts while providing specific, executable patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting only actionable patterns without explaining basic Java concepts. Every section provides direct examples without unnecessary preamble or explanation of what Claude already knows. | 3 / 3 |
Actionability | Provides concrete, executable Java code examples throughout. Each pattern shows both the correct approach (✅) and anti-patterns (❌) with copy-paste ready code snippets. | 3 / 3 |
Workflow Clarity | This is a coding standards skill, not a multi-step workflow. The single purpose (defining Java coding standards) is unambiguous, with clear organization by topic. No destructive or batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a standards document under 100 lines, the content is well-organized into logical sections with clear headers. No external references are needed as the skill is self-contained and appropriately scoped. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%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.
- Reviewed
Table of Contents
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.