CtrlK
BlogDocsLog inGet started
Tessl Logo

kotlin-backend-conventions

编写 BK-CI Kotlin 后端代码时使用,例如 Kotlin 文件结构、格式、命名、函数设计、空安全和 BK-CI 项目内的调用约定。当用户要修改 `.kt` 或 `.kts` 后端代码并需要项目级 Kotlin 规范时优先使用。

77

Quality

96%

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

92%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.

A well-organized, lean conventions skill that routes to three clearly-signaled reference files and states concrete high-signal rules. Its only gap is that most actionable detail lives in the references rather than inline, slightly limiting standalone actionability.

Suggestions

Inline 2-3 concrete Kotlin code do/don't snippets (e.g. wildcard import vs explicit imports, named-argument call) so the skill is actionable without opening every reference file.

Note in 延伸阅读 that the three reference/ files are the canonical source, so Claude knows where authoritative rules live when references and quick-guide bullets disagree.

Add a one-line validation cue for convention changes (e.g. run ktlint/detekt to confirm) so edits can be self-checked.

DimensionReasoningScore

Conciseness

The body is lean — short bullets, no padding, no explaining what Kotlin is — and explicitly instructs not to repeat formatter/static-check rules ("能交给格式化工具和静态检查的规则,不要在主 skill 里重复展开"), so every token earns its place.

5 / 5

Actionability

It gives concrete named rules ("禁止 wildcard import", "命名参数", "避免完整类路径直接调用") and clear pointers to three reference files, but the bulk of actionable detail is delegated to those references rather than given inline.

4 / 5

Workflow Clarity

The 快速指导 section provides a clear five-step sequenced usage guide for a single-purpose skill under 50 lines; no destructive/batch operations are involved so no validation checkpoints are required, satisfying the simple-skill exception.

5 / 5

Progressive Disclosure

The SKILL.md acts as a clear overview pointing to three well-signaled, one-level-deep reference files (1-file-format-import.md, 2-naming-function-design.md, 3-null-safety-project-practice.md) listed in both 快速指导 and 延伸阅读, making navigation easy.

5 / 5

Total

19

/

20

Passed

Description

100%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.

A tight, well-scoped description that clearly answers both what and when with concrete trigger terms and file extensions. It is distinct from neighboring skills and uses neutral third-person voice throughout.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete concerns — "Kotlin 文件结构、格式、命名、函数设计、空安全和 BK-CI 项目内的调用约定" — giving comprehensive coverage of the skill's scope rather than vague abstraction.

5 / 5

Completeness

It explicitly states both what (governs Kotlin file structure, formatting, naming, function design, null safety, calling conventions) and when ("当用户要修改 `.kt` 或 `.kts` 后端代码并需要项目级 Kotlin 规范时优先使用") with concrete trigger phrases, in neutral third-person voice.

5 / 5

Trigger Term Quality

It includes natural user phrases ("修改 `.kt` 或 `.kts` 后端代码", "Kotlin 规范", "BK-CI Kotlin 后端代码") plus file extensions .kt/.kts, covering synonyms and extensions users would actually say.

5 / 5

Distinctiveness Conflict Risk

The niche is tightly scoped to BK-CI Kotlin backend code with distinct file-extension triggers, minimizing overlap with general backend, Spring Boot, or testing skills.

5 / 5

Total

20

/

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
TencentBlueKing/bk-ci
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.