CtrlK
BlogDocsLog inGet started
Tessl Logo

code-method-normalize

规范化新生成或改写的 Java/Kotlin 方法:Java 用 JavaDoc、Kotlin 用 KDoc,两套规则不混用; Java 入参 final(抽象方法、接口默认方法、@Override 实现除外一律不加); 方法注释与备注同一套结构:首段/首行无内联代码与类型引用,补充说明用 <pre> 包裹; 有返回值且带参时补全 @param/@return;Kotlin 的 @param 行不写 [类型](签名已标明);boolean 的 @return:Java 用 {@code true}/{@code false},Kotlin 用 `true`/`false`; 类型引用:Java {@link …},Kotlin @return/<pre> 等用 […];优先返回入参或有语义的对象替代无意义 void;异常在方法内捕获并安全返回。 在用户要求规范化方法、统一工具类写法、整理 Javadoc/KDoc、或按 DevUtils 方法风格处理时使用。

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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

A concrete, actionable rule set with executable Java/Kotlin examples and an explicit self-test checklist, well-organized into clear sections. Its main weakness is redundancy — the same rules are restated in the description, a summary paragraph, and the checklist — which inflates token cost without adding information.

Suggestions

Remove the '要点' summary paragraph in section 5.3, since it restates rules already shown in the adjacent code examples and earlier sections; let the examples carry the point.

Cross-reference the section 8 checklist against sections 0–7 and drop any checklist item that merely duplicates a heading-level rule, keeping only items that serve as a genuine verification gate.

Tighten section 5.1's enumeration of forbidden reference forms, which overlaps with the section 4 table; consolidate so each rule appears in exactly one canonical location.

DimensionReasoningScore

Conciseness

The body is rule-dense and avoids explaining concepts Claude already knows, but the same rules are restated across the description, the section 5.3 '要点' summary, and the section 8 checklist, so it could be tightened — matching the score-2 'mostly efficient but could be tightened' anchor rather than score 3 where every token earns its place.

2 / 3

Actionability

Provides concrete right/wrong pairs (section 2.1 错误/正确), copy-paste templates (sections 3.1/3.2), and full Java+Kotlin code examples (section 5.3), matching the score-3 'fully executable, copy-paste ready' anchor rather than the pseudocode/incomplete score-2 anchor.

3 / 3

Workflow Clarity

Section 8 '执行清单(改写方法时自测)' is an explicit verification checklist for the rewrite task, and the single action is unambiguous, matching the score-3 'checklists for complex processes' anchor; not score 2 since checkpoints are explicit rather than implicit.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is a single cohesive cross-language ruleset, well-sectioned with headers/tables and no nested or broken references; per the simple-skills note, well-organized sections with no need for external references score 3, so it is not the monolithic/poorly-organized score-1 or should-be-split score-2 anchor.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-triggered description that concretely states both the normalization actions and when to use the skill, with a clear niche unlikely to collide with other skills. Voice is appropriately third-person/directive with no first/second-person phrasing.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions (Java 入参 final, 补全 @param/@return, boolean 的 @return Java {@code true}/{@code false}, 异常在方法内捕获并安全返回), matching the 'lists multiple specific concrete actions' anchor rather than the score-2 domain-only anchor.

3 / 3

Completeness

It clearly answers both what (the normalization rules) and when (the explicit '…时使用' trigger clause), matching the score-3 'both what AND when with explicit triggers' anchor rather than score 2 where 'when' is only implied.

3 / 3

Trigger Term Quality

The explicit clause '在用户要求规范化方法、统一工具类写法、整理 Javadoc/KDoc、或按 DevUtils 方法风格处理时使用' gives good coverage of natural trigger phrases a user in this niche would say, matching the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche (Java/Kotlin method-documentation normalization) with distinct triggers, making conflict with other skills unlikely; matches the score-3 'clear niche with distinct triggers' anchor.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
afkT/DevUtils
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.