Individual skill
kotlin-concurrency-and-flow
Use when writing or reviewing Kotlin coroutine scope ownership, raw Thread or Executor work, init launches, non-suspending launch APIs, runBlocking, cancellation, StateFlow, SharedFlow, Channel, stateIn, SharingStarted, state updates, or one-shot events.
skills/kotlin-concurrency-and-flow/SKILL.md
Source commit d83f6e289a07a55026e610c797672f22eff3f022
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,145
- Repository last updated
- Nov 5, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- android Repository topic
- compose-multiplatform Repository topic
- coroutines Repository topic
- jetpack-compose Repository topic
- kotlin Repository topic
- kotlin-multiplatform Repository topic
- skills Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,856 bytesreferences/flow-state-events.mddoc · 2,883 bytesreferences/structured-concurrency.mddoc · 5,218 bytes
Read excerpt
# Kotlin concurrency and Flow
## Core principle
Give asynchronous work an explicit owner and lifetime, then model durable state
and transient events with primitives whose delivery and replay semantics match
the product contract.
## Procedure
1. Identify each coroutine owner, cancellation boundary, producer, consumer,
durable state, and transient event.
2. Before changing an API, compare its existing caller-visible contract with
the required owner and lifetime. If a suspend API already gives its caller