android-coroutines
Authoritative rules and patterns for production-quality Kotlin Coroutines onto Android. Covers structured concurrency, lifecycle integration, and reactive streams.
59
48%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/android-coroutines/SKILL.mdQuality
Discovery
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 a clear technical domain (Kotlin Coroutines on Android) and lists relevant topic areas, but lacks concrete actions and explicit trigger guidance. It reads more like a topic summary than actionable skill selection criteria, making it difficult for Claude to know precisely when to choose this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when implementing coroutines in Android, handling async operations, or when the user mentions suspend functions, Flow, viewModelScope, or coroutine exceptions'.
Replace topic areas with concrete actions: 'Implements coroutine scopes, handles cancellation, converts callbacks to suspend functions, integrates Flow with UI lifecycle'.
Include common user terminology variations: 'async/await patterns', 'background tasks', 'suspend functions', 'Flow', 'StateFlow', 'SharedFlow'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kotlin Coroutines on Android) and mentions some areas (structured concurrency, lifecycle integration, reactive streams), but these are topic areas rather than concrete actions like 'implement', 'debug', or 'convert'. | 2 / 3 |
Completeness | Describes what it covers (rules and patterns for coroutines) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Kotlin Coroutines', 'Android', 'structured concurrency', 'lifecycle', 'reactive streams', but misses common user variations like 'async', 'suspend functions', 'Flow', 'viewModelScope', 'coroutine scope'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Kotlin Coroutines' and 'Android' provides some distinctiveness, but 'reactive streams' could overlap with RxJava skills, and general Android development skills might also cover coroutines. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable guidance for Android Coroutines with excellent code examples and clear rules. However, it includes unnecessary meta-content (responsibilities, applicability sections) that Claude doesn't need, and lacks explicit workflows with validation steps for implementing these patterns in practice. The content would benefit from trimming introductory sections and adding verification guidance.
Suggestions
Remove or significantly trim the 'Responsibilities' and 'Applicability' sections - Claude can infer when to apply these patterns
Add a brief workflow section showing how to verify implementations (e.g., 'Run tests with TestDispatcher to verify main-safety')
Consider splitting advanced topics (callbackFlow patterns, exception handling edge cases) into a linked ADVANCED.md file
Remove explanatory text like 'Coroutines feature cooperative cancellation' - state the rule directly without the concept explanation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary framing (e.g., 'Responsibilities', 'Applicability' sections that describe when to use rather than how). The rules themselves are reasonably concise, but the introductory content and some explanations (like explaining what cooperative cancellation means) add tokens Claude already knows. | 2 / 3 |
Actionability | Provides fully executable Kotlin code examples for each major pattern (repository, parallel execution, testing). Code is copy-paste ready with correct syntax and demonstrates both correct and incorrect approaches clearly. | 3 / 3 |
Workflow Clarity | Rules are clearly enumerated and patterns are well-structured, but there's no explicit workflow for implementing coroutines in a new feature or migrating existing code. Missing validation checkpoints for verifying correct implementation (e.g., how to verify main-safety or test for leaks). | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but it's a monolithic file with no references to external documentation for advanced topics. The testing section could be expanded in a separate file, and error handling patterns could benefit from deeper examples in a linked reference. | 2 / 3 |
Total | 9 / 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.