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 方法风格处理时使用。

72

Quality

87%

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

82%Weight 40%Scale 1-5

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

The body is highly actionable with complete Java/Kotlin examples and explicit verification via a self-test checklist, and is well-structured into numbered sections. The main weaknesses are mild cross-section redundancy and the absence of an explicit validate→fix→retry feedback loop.

Suggestions

Reduce redundancy between the section-2.1/4/5 prose and the section-8 checklist by cross-referencing instead of restating, to improve conciseness.

Add an explicit validate→fix→retry loop (e.g., 'after rewriting, run the section-8 checklist; if any item fails, fix and re-check before finishing') to lift workflow clarity.

Consider moving the full Java/Kotlin reference examples in section 5.3 into a separate references file to strengthen progressive disclosure.

DimensionReasoningScore

Conciseness

Dense, rule-focused prose that does not pad with concepts Claude already knows, but several rules are restated across the prose (sections 2.1, 4, 5) and the section-8 checklist, adding some redundancy that could be trimmed — fitting 'efficient; minor instances of over-explanation' rather than the fully lean 5.

4 / 5

Actionability

Provides copy-paste-ready, complete examples — full Java and Kotlin methods in section 5.3, explicit 正确/错误 @param pairs, boolean @return templates, and a final self-test checklist — covering the common cases with executable guidance.

5 / 5

Workflow Clarity

Rules are clearly organized into numbered sections and the section-8 '执行清单(改写方法时自测)' provides explicit verification checkpoints, but there is no validate→fix→retry feedback loop, so it sits at 'clear sequence with most checkpoints present; minor validation gaps' rather than 5.

4 / 5

Progressive Disclosure

Single-file content (~165 lines) with well-organized section headers, tables, and a checklist and no broken or buried references (no bundle files exist); structure is good, though some example material could conceivably live in a separate reference, fitting 'good structure; most content appropriately placed' above the 3 anchor.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

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, complete, and distinctive: it states a comprehensive set of concrete normalization rules and an explicit 'use when' clause with multiple natural trigger phrases. The only mild gap is trigger-term breadth, where a few extra synonyms could be added.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with comprehensive coverage: 'Java 入参 final', '补全 @param/@return', 'boolean 的 @return', '类型引用 Java {@link}/Kotlin […]', '异常在方法内捕获并安全返回'. Matches the 'multiple specific concrete actions; comprehensive coverage' anchor and is not merely a minor-gap (4) list.

5 / 5

Completeness

Explicitly answers both what (the full normalization rule set) and when — '在用户要求规范化方法、统一工具类写法、整理 Javadoc/KDoc、或按 DevUtils 方法风格处理时使用' — with concrete trigger phrases, matching the 'clearly and explicitly answers both what AND when' anchor.

5 / 5

Trigger Term Quality

Provides several natural trigger phrases a user would say — '规范化方法', '统一工具类写法', '整理 Javadoc/KDoc', 'DevUtils 方法风格' — giving good coverage, though a few common synonyms/variations are absent, fitting 'good keyword coverage; a few natural terms missing' rather than the fully comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

Targets a very specific niche (Java/Kotlin method normalization per DevUtils style with JavaDoc/KDoc rules and final-param exceptions), yielding a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

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.