CtrlK
BlogDocsLog inGet started
Tessl Logo

java-coding-standards

适用于 Spring Boot 服务的 Java 编码规范:命名、不可变性、Optional 使用、流(Stream)、异常、泛型及项目布局。

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/ja-JP/skills/java-coding-standards/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The content is a tight, actionable coding-standards reference with executable examples and clean single-file organization; its only gap is the absence of any multi-step workflow with validation checkpoints, which is largely N/A for this skill type.

DimensionReasoningScore

Conciseness

The body is lean and code-forward: short bullets plus executable Java snippets, with no padding or explanation of concepts Claude already knows (e.g. it never defines what a record or stream is).

3 / 3

Actionability

It provides concrete, executable Java patterns — records, Optional map/orElseThrow, stream pipelines, bounded generics, LoggerFactory logging — that are copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

This is a reference/standards document with no multi-step workflow to sequence; it is well-organized but lacks the explicit step sequence and validation checkpoints the score-3 anchor requires.

2 / 3

Progressive Disclosure

All content sits in one well-organized SKILL.md with clearly headed sections and no nested or broken references, which is appropriate for a single-file standards reference.

3 / 3

Total

11

/

12

Passed

Description

65%

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 uses natural trigger terms, but it omits an explicit 'Use when…' activation clause, which caps completeness and distinctiveness at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing or reviewing Java code in Spring Boot services, or when enforcing naming, immutability, Optional, stream, exception, or generics conventions.'

Reframe the topic list as concrete actions (e.g. 'Enforce naming conventions, prefer records/final fields for immutability, return Optional from find* methods') to lift specificity from 2 to 3.

Include the Java 17+ qualifier and a Spring-specific cue in the description to sharpen distinctiveness against generic Java-standards skills.

DimensionReasoningScore

Specificity

The description names a clear domain (Spring Boot Java) and lists specific topics ("命名、不可变性、Optional 使用、流、异常、泛型以及项目布局"), but these are topic categories rather than concrete actions like 'extract' or 'fill', so it does not reach the multiple-concrete-actions anchor.

2 / 3

Completeness

It clearly states what the skill covers but lacks any explicit "Use when…" trigger clause, so per the rubric guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

It surfaces natural terms a developer would say — "Spring Boot", "Java 编码规范", "命名", "异常", "Optional", "流 (streams)", "泛型" — giving good coverage of relevant trigger vocabulary.

3 / 3

Distinctiveness Conflict Risk

The Spring Boot + Java coding-standards niche is fairly specific, but without explicit triggers it could still overlap a generic Java-standards skill, matching the 'somewhat specific but could overlap' anchor.

2 / 3

Total

9

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
xu-xiang/everything-claude-code-zh
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.