kotlin-concurrency-expert
Kotlin Coroutines review and remediation for Android. Use when asked to review concurrency usage, fix coroutine-related bugs, improve thread safety, or resolve lifecycle issues in Kotlin/Android code.
96
95%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 well-structured skill description with explicit 'Use when...' guidance and good trigger term coverage for the Kotlin/Android coroutines domain. The main weakness is that the capability description could be more specific about concrete actions (e.g., specific coroutine patterns, scope management, dispatcher usage) rather than general categories like 'review' and 'fix'.
Suggestions
Add more specific concrete actions like 'migrate GlobalScope to structured concurrency', 'implement proper cancellation handling', or 'fix dispatcher usage for UI updates' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kotlin Coroutines, Android) and mentions actions like 'review', 'fix', 'improve', 'resolve', but doesn't list multiple specific concrete actions like 'cancel jobs on lifecycle events' or 'migrate from GlobalScope to viewModelScope'. | 2 / 3 |
Completeness | Clearly answers both what ('Kotlin Coroutines review and remediation for Android') and when ('Use when asked to review concurrency usage, fix coroutine-related bugs, improve thread safety, or resolve lifecycle issues'). Has explicit 'Use when...' clause with specific triggers. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'concurrency', 'coroutine', 'thread safety', 'lifecycle issues', 'Kotlin', 'Android'. Good coverage of terms developers would naturally use when encountering these problems. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting Kotlin Coroutines specifically on Android platform. The combination of 'coroutine', 'lifecycle issues', and 'Kotlin/Android' creates distinct triggers unlikely to conflict with general code review or other language-specific skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates best practices for technical documentation. It's concise yet comprehensive, with executable code examples showing both correct and incorrect patterns. The structured workflow, clear scope guidelines table, and testing pattern make it immediately actionable for coroutine-related issues.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with Kotlin/Android. No unnecessary explanations of what coroutines are or how they work—jumps straight to actionable patterns and anti-patterns. | 3 / 3 |
Actionability | Every section provides executable, copy-paste ready Kotlin code with clear CORRECT/INCORRECT comparisons. The common fixes list is specific and directly applicable to real issues. | 3 / 3 |
Workflow Clarity | The two-step workflow (Triage → Apply Fix) is clear and appropriate for this diagnostic/remediation skill. Each step has explicit checkpoints (verify dispatcher injection, confirm scope context) before proceeding to fixes. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Overview, Workflow, Critical Rules, Scope Guidelines, Testing Pattern). External references are one level deep and clearly signaled at the end. The scope table provides excellent quick-reference navigation. | 3 / 3 |
Total | 12 / 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.
- Commit
3f68e39
- 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.