kotlin-coroutines-flows

Kotlin Coroutines and Flow patterns for Android and KMP — structured concurrency, Flow operators, StateFlow, error handling, and testing.

Quality

81%

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

The canonical home for this skill is tdg-personal/kotlin-coroutines-flows

Quality

Content

80%

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

A high-quality, actionable patterns catalog with lean code examples, held back slightly by the lack of a gated multi-step workflow and the absence of file-level progressive disclosure.

Suggestions

For multi-step risky operations (e.g., retry/cancellation flows), add explicit validate-then-proceed checkpoints or a short checklist.

Consider splitting the larger sections (Flow Patterns, Testing) into reference files and linking to them from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward, assumes Kotlin competence, and avoids explaining concepts Claude already knows; nearly every prose line earns its place.	3 / 3
Actionability	It provides complete, executable, copy-paste-ready Kotlin examples (loadDashboard, stateIn, combine, retryWhen, Turbine tests, fakes) rather than pseudocode or vague direction.	3 / 3
Workflow Clarity	Content is logically sequenced by topic and the testing section offers verification, but there is no explicit multi-step workflow with validation checkpoints or feedback loops for complex operations.	2 / 3
Progressive Disclosure	Sections are well-organized with a clear overview, but all content is inline with no file-level split, and the References point to sibling skills rather than bundle files.	2 / 3
	Total	10 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-targeted description with strong trigger terms and a clear niche, weakened only by the absence of an explicit "Use when..." clause that would lock in full completeness.

Suggestions

Append an explicit trigger clause, e.g. "Use when writing async or reactive Kotlin code with coroutines, Flow, StateFlow, or SharedFlow in Android or KMP projects."

Dimension	Reasoning	Score
Specificity	The description lists multiple specific concrete capabilities — "structured concurrency, Flow operators, StateFlow, error handling, and testing" — naming distinct Kotlin constructs rather than vague abstractions.	3 / 3
Completeness	The "what" is explicit, but there is no "Use when..." clause or equivalent explicit trigger guidance, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	It uses natural terms developers actually say — "Kotlin Coroutines", "Flow", "StateFlow", "Android", "KMP" — giving good coverage of likely trigger language.	3 / 3
Distinctiveness Conflict Risk	"Kotlin Coroutines and Flow patterns for Android and KMP" carves a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/kotlin-coroutines-flows/SKILL.md
Commit: 754b8dd

Reviewed: 2 days 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.