It names the domain (Android ViewModel/View integration) and mentions some specific mechanisms (Coroutines, Lifecycle, repeatOnLifecycle), but doesn't list multiple concrete actions—it describes a general integration task rather than specific operations like 'collect StateFlow', 'observe LiveData', 'launch coroutines in lifecycleScope'.

Clearly answers both 'what' (integrate ViewModel state with Views using Coroutines and Lifecycle on Android) and 'when' (explicit 'Use when managing state with repeatOnLifecycle or lifecycle-aware coroutines in Fragment/Activity').

Includes strong natural keywords a developer would use: 'ViewModel', 'Coroutines', 'Lifecycle', 'repeatOnLifecycle', 'Fragment', 'Activity', 'lifecycle-aware coroutines', 'state'. These are terms Android developers naturally use when seeking help with this pattern.

Targets a very specific niche—Android lifecycle-aware coroutine state collection in Fragment/Activity with repeatOnLifecycle. This is unlikely to conflict with general Android, general coroutines, or general ViewModel skills due to the precise combination of triggers.

Very lean and efficient. Every line adds value—no explanation of what Flows or LiveData are, no unnecessary context. The 'Why' line is justified as it explains a non-obvious safety concern specific to this pattern.

Provides clear rules and anti-patterns but lacks executable code examples. A concrete code snippet showing repeatOnLifecycle usage would make this copy-paste ready rather than requiring the reader to look up the implementation template.

This is a simple, single-purpose skill (state collection pattern) with no multi-step destructive process. The rules and anti-patterns are unambiguous, and the single action (use repeatOnLifecycle) is clear.

Clean overview with a single well-signaled reference to the implementation template. Content is appropriately split—rules and anti-patterns inline, detailed implementation in a separate file one level deep.