kotlin-specialist
Provides idiomatic Kotlin implementation patterns including coroutine concurrency, Flow stream handling, multiplatform architecture, Compose UI construction, Ktor server setup, and type-safe DSL design. Use when building Kotlin applications requiring coroutines, multiplatform development, or Android with Compose. Invoke for Flow API, KMP projects, Ktor servers, DSL design, sealed classes, suspend function, Android Kotlin, Kotlin Multiplatform.
91
92%
Does it follow best practices?
Impact
88%
1.12xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly communicates specific Kotlin capabilities, provides explicit trigger guidance with both 'Use when' and 'Invoke for' clauses, and includes a comprehensive set of natural keywords that Kotlin developers would use. The description is well-structured, uses third person voice correctly, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and patterns: coroutine concurrency, Flow stream handling, multiplatform architecture, Compose UI construction, Ktor server setup, and type-safe DSL design. These are all distinct, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (idiomatic Kotlin patterns for coroutines, Flow, multiplatform, Compose, Ktor, DSLs) and 'when' with explicit 'Use when...' and 'Invoke for...' clauses listing specific trigger scenarios and terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'coroutines', 'Flow API', 'KMP projects', 'Ktor servers', 'DSL design', 'sealed classes', 'suspend function', 'Android Kotlin', 'Kotlin Multiplatform', 'Compose'. These are the exact terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in Kotlin-specific patterns. The combination of Kotlin-specific technologies (coroutines, Flow, KMP, Ktor, Compose) makes it very unlikely to conflict with general programming or other language-specific skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured Kotlin skill with strong progressive disclosure via the reference table, clear workflow with validation checkpoints, and executable code examples. Its main weakness is moderate verbosity—the scope functions section, null safety patterns, and knowledge reference list explain things Claude already knows well. The constraints section, while useful, could be more concise.
Suggestions
Trim or remove the scope functions section and null safety basics, as these are fundamental Kotlin concepts Claude already knows—focus constraint guidance on the non-obvious rules (e.g., '!! only with documented justification').
Remove the 'Knowledge Reference' keyword list at the bottom, as it provides no actionable guidance and duplicates information already conveyed by the reference table and code examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content. The 'Knowledge Reference' section at the bottom is just a keyword list that adds little value. The constraints section has some items Claude would already know (e.g., 'Document public APIs with KDoc'). The scope functions section explains basic concepts Claude already understands well. However, the code examples are tight and the reference table is efficient. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready Kotlin code examples for sealed classes, coroutines/Flow, null safety, and scope functions. Anti-patterns are clearly marked with comments. The constraints section gives specific, concrete do/don't guidance. The reference table provides clear pointers to detailed guidance files. | 3 / 3 |
Workflow Clarity | The core workflow has a clear 6-step sequence with an explicit validation checkpoint at step 3 (verify coroutine cancellation and null safety) and a feedback loop at step 4 (if detekt/ktlint fails, fix and re-run before proceeding). This covers the validate-fix-retry pattern well for a development workflow. | 3 / 3 |
Progressive Disclosure | Excellent use of a reference table that clearly signals when to load each detailed reference file, with one-level-deep references. The main SKILL.md provides a concise overview with key patterns inline while deferring detailed topic-specific guidance to five separate reference files with clear 'Load When' conditions. | 3 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
3d95bb1
- 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.