kotlin-patterns

Patrones idiomáticos de Kotlin, buenas prácticas y convenciones para construir aplicaciones Kotlin robustas, eficientes y mantenibles con coroutines, null safety y builders de DSL.

Quality

55%

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 ./docs/es/skills/kotlin-patterns/SKILL.md

Quality

Content

57%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 a comprehensive, well-structured Kotlin patterns reference with concrete Bien/Mal code examples and a fully specified Gradle block, making it highly actionable. Its main weaknesses are length and duplicated examples, the absence of an explicit procedural workflow with checkpoints, and no progressive disclosure via separate reference files.

Suggestions

Remove duplicated examples (the Result sealed class and fetchUserWithPosts each appear twice) and tighten basic-concept intros to reduce token cost.

Move large reference blocks (e.g., the full build.gradle.kts Gradle Kotlin DSL section and the DSL builder examples) into separate reference files under references/ and link to them from SKILL.md.

For destructive or batch-prone patterns (e.g., coroutine cancellation cleanup, GlobalScope avoidance), add explicit validation/checkpoint steps so the workflow dimension can rise above 3.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight code examples with short intros, but it is very long (~700 lines) and contains clear redundancy (the Result sealed class and the fetchUserWithPosts example each appear twice), plus a few basic-concept statements Claude already knows, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean anchor 4.	3 / 5
Actionability	Concrete, copy-paste-ready Kotlin examples with Bien/Mal pairs across every topic and a fully specified Gradle Kotlin DSL block with real plugin/version values, but some examples depend on undefined domain types (userRepository, userService, AppError), placing it at 'mostly executable guidance; concrete code with minor gaps' rather than fully executable.	4 / 5
Workflow Clarity	This is a topical patterns reference rather than a sequenced workflow; it is well organized via Cuándo Usar, Principios Fundamentales, and Anti-Patrones, but there is no procedural sequence with validation checkpoints, matching 'sequence present but checkpoints missing or implicit'; no destructive/batch cap applies.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and all content is inlined in a single ~700-line SKILL.md; section headers provide good structure, but content that could live in separate reference files (e.g., the full Gradle block, DSL builders) is inline with no one-level-deep references, fitting 'some structure but content that should be separate is inline'.	3 / 5
	Total	13 / 20 Passed

Description

53%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 clearly identifies the Kotlin niche and several concrete technical areas, but lacks an explicit 'Use when' trigger clause and leans on topic modifiers rather than discrete action verbs. It is distinguishable but would benefit from explicit trigger phrases and broader synonym coverage.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations (e.g., writing, reviewing, or refactoring Kotlin code, or setting up a Gradle Kotlin DSL build).

Replace or supplement the generic 'construir aplicaciones' with discrete action verbs (e.g., 'Apply, review, and refactor Kotlin code').

Broaden trigger term coverage with natural synonyms users say (refactor, code review, coroutines/Flow, sealed classes, data classes, extension functions).

Dimension	Reasoning	Score
Specificity	Names the Kotlin domain and several concrete technical areas ('coroutines, null safety y builders de DSL'), but the only action verb is the generic 'construir aplicaciones' while the listed items are topics/modifiers rather than discrete actions, matching the 'names domain and 1-2 concrete actions' anchor rather than the multi-action anchor 4.	3 / 5
Completeness	It clearly answers 'what' (idiomatic patterns and conventions for robust Kotlin apps) but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3; this matches the 'clear what but when is missing or only weakly implied' anchor.	3 / 5
Trigger Term Quality	Includes natural terms a Kotlin user would say ('Kotlin', 'coroutines', 'null safety', 'DSL', 'patrones idiomáticos'), but misses common variations and synonyms such as refactor, review, Flow, sealed classes, data classes, and extension functions, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Kotlin-specific technical triggers (coroutines, null safety, DSL builders) carve a clear niche with minimal conflict risk, though the broad 'buenas prácticas y convenciones' phrasing leaves minor overlap with generic code-review or best-practices skills, placing it at 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (712 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: docs/es/skills/kotlin-patterns/SKILL.md
Commit: c70874f

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.