kotlin-development

Kotlin development guidelines with best practices for clean code, naming conventions, function design, and data handling

Quality

33%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./kotlin-development/SKILL.md

Quality

Content

35%

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

This skill reads as a generic clean code style guide lightly branded for Kotlin, with no actual Kotlin code examples, no executable snippets, and heavy reliance on principles Claude already knows (SOLID, AAA testing, composition over inheritance). The lack of Kotlin-specific actionable content—such as idiomatic patterns, sealed classes, coroutines, extension functions, or scope functions—makes it low-value as a skill file.

Suggestions

Add concrete Kotlin code examples for each guideline (e.g., show a data class with validation, demonstrate early returns with Kotlin's `?.let` or `takeIf`, show idiomatic use of `sealed class` for error handling).

Remove generic software engineering advice Claude already knows (SOLID, AAA, composition over inheritance) and replace with Kotlin-specific idioms and patterns that are genuinely additive.

Include before/after code examples showing bad vs. good Kotlin patterns to make guidelines actionable rather than abstract.

Add Kotlin-specific content such as coroutine usage guidelines, scope function conventions (let/run/apply/also/with), sealed class patterns, and extension function best practices.

Dimension	Reasoning	Score
Conciseness	The content is reasonably organized but includes many guidelines Claude already knows well (SOLID principles, Arrange-Act-Assert, composition over inheritance, single responsibility). Some sections like 'Exception Handling' and 'Testing' are largely restating standard software engineering knowledge without Kotlin-specific value.	2 / 3
Actionability	The skill is entirely abstract guidelines with no executable code examples, no Kotlin-specific syntax demonstrations, and no concrete before/after examples. Statements like 'Use data classes for data structures' and 'Follow SOLID principles' are vague directions rather than actionable instructions with Kotlin code.	1 / 3
Workflow Clarity	For a guidelines/conventions skill, there's no multi-step workflow needed, but the sections are clearly organized with logical grouping. However, there's no guidance on how to apply these rules in practice—no decision trees, no priority ordering when rules conflict, and no validation steps for checking compliance.	2 / 3
Progressive Disclosure	The content is organized into clear sections with headers, which is good. However, it's a monolithic document with no references to supporting files, and some sections (like Testing, Exception Handling) could be split out or condensed since they contain generic advice rather than Kotlin-specific guidance.	2 / 3
	Total	7 / 12 Passed

Description

32%

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 identifies the domain (Kotlin) and lists broad topic areas but reads more like a document title than a skill description. It lacks concrete actions, explicit trigger guidance, and sufficient specificity to distinguish it from general coding best practices skills for other languages.

Suggestions

Add a 'Use when...' clause specifying triggers, e.g., 'Use when writing or reviewing Kotlin code, asking about Kotlin style conventions, or working with .kt files.'

Replace vague category names with concrete actions, e.g., 'Enforces Kotlin naming conventions, recommends idiomatic function design patterns, guides null-safe data handling and use of data classes.'

Include natural trigger terms users would say, such as 'Kotlin style', 'Kotlin best practices', 'idiomatic Kotlin', '.kt files', or 'Kotlin code review'.

Dimension	Reasoning	Score
Specificity	Names the domain (Kotlin development) and lists some areas (clean code, naming conventions, function design, data handling), but these are broad categories rather than concrete actions. It doesn't specify what actions are performed, like 'enforces naming conventions' or 'reviews function signatures'.	2 / 3
Completeness	Describes what the skill covers at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak (guidelines rather than actions), so this scores a 1.	1 / 3
Trigger Term Quality	Includes 'Kotlin' as a strong trigger term and some relevant phrases like 'naming conventions' and 'clean code' that users might mention. However, it misses common variations like '.kt files', 'Kotlin style', 'code review', 'linting', or 'coding standards'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Kotlin' provides some distinctiveness, but 'clean code, naming conventions, function design, and data handling' are generic software development concepts that could overlap with coding style guides for any language.	2 / 3
	Total	7 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: mindrally/skills
Path: kotlin-development/SKILL.md
Commit: 05a7130

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.