CtrlK
BlogDocsLog inGet started
Tessl Logo

java-coding-standards

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

60

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The content is concise and highly actionable, with real Java examples that assume Claude's competence and avoid concept over-explanation. Its weaknesses are structural: as a single monolithic file with no progressive disclosure and no procedural workflow, it scores lower on workflow clarity and file navigation.

Suggestions

Split the deeper topic sections (e.g. exceptions, generics, project layout) into reference files linked from a concise overview in SKILL.md to improve progressive disclosure.

Since this is a reference rather than a procedure, consider adding a short 'how to apply these standards during a code review' workflow with a validation checkpoint (e.g. 'verify each item against the checklist before approving') to raise workflow clarity.

Replace the few partial snippets (e.g. `indexById(...) { ... }` and the comment-only stream FAIL) with complete, runnable examples or explicitly mark them as illustrative.

DimensionReasoningScore

Conciseness

The body is lean — short bullets with compact PASS/FAIL code examples and no padding explaining basic Java concepts (records, streams, Optional), matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Provides concrete, executable Java such as `Optional<Market> market = marketRepository.findBySlug(slug);` and a stream pipeline ending in `.toList()`, plus real exception/logging snippets — predominantly copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

This is a standards reference, not a multi-step process, so there is no sequenced workflow or validation checkpoint; sections are well-organized but no procedural sequence exists, placing it at the 'steps present but checkpoints missing' level rather than 3.

2 / 3

Progressive Disclosure

Everything lives in a single ~134-line SKILL.md with no references/scripts/assets bundle files; internal sections are well-organized, but at over 50 lines with no file split or one-level-deep references it does not reach the progressive-disclosure anchor of 3.

2 / 3

Total

10

/

12

Passed

Description

57%

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 occupies a clear niche, but it catalogs covered topics rather than concrete actions and lacks any explicit trigger guidance for when to invoke the skill. Adding a 'Use when…' clause would lift completeness and trigger-term quality.

Suggestions

Append a 'Use when…' trigger clause, e.g. 'Use when writing or reviewing Java/Spring Boot service code, or when the user asks about naming, immutability, Optional, streams, exceptions, or project layout.'

Reframe the topic list toward concrete actions where possible (e.g. 'apply naming conventions, enforce immutability with records, return Optional from find methods') rather than only naming topic areas.

Add natural keyword variations users might say ('Java conventions', 'Spring Boot style guide', 'code review Java') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists specific topics ("命名、不変性、Optional使用、ストリーム、例外、ジェネリクス、プロジェクトレイアウト") for a defined domain, but these are topic areas rather than concrete actions like extract/fill/merge, so it sits at the 'names domain and some actions' anchor rather than 3.

2 / 3

Completeness

Clearly states what the skill covers ("Spring Bootサービス向けのJavaコーディング標準") but provides no explicit "when should Claude use it" clause, so per the guideline a missing 'Use when' caps completeness at 2.

2 / 3

Trigger Term Quality

Contains natural terms a user would say ("Spring Boot", "Java", "コーディング標準") but offers no "Use when…" phrasing or common variations, matching the 'some relevant keywords but missing variations' anchor.

2 / 3

Distinctiveness Conflict Risk

"Spring Bootサービス向けのJavaコーディング標準" names a clear, narrow niche with distinct triggers (Spring Boot + Java coding standards) that is unlikely to conflict with unrelated skills.

3 / 3

Total

9

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/everything-claude-code
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.