The description names the domain (Android state management with ViewModels, Coroutines, Lifecycle) and a general action ('Integrate State with Views'), but does not list multiple specific concrete actions like collecting flows, observing LiveData, setting up lifecycle-aware coroutine scopes, etc.

Clearly answers both 'what' (integrate state with views using coroutines and lifecycle on Android) and 'when' (explicit 'Use when managing state with ViewModels and Lifecycle-aware coroutines in Android' plus file pattern triggers). The triggers clause provides additional explicit guidance.

Includes strong natural keywords users would encounter or type: 'Fragment.kt', 'Activity.kt', 'repeatOnLifecycle', 'launchWhenStarted', 'ViewModels', 'Lifecycle-aware coroutines', 'Android'. These are terms developers naturally use when working in this area.

Highly specific niche: Android lifecycle-aware coroutine state management with explicit file patterns (*Fragment.kt, *Activity.kt) and specific API references (repeatOnLifecycle, launchWhenStarted). Unlikely to conflict with other skills.

Very lean and efficient. Every line adds value—no explanation of what Flows or LiveData are, no unnecessary context. The 'Why' annotations are brief and justify the rules without over-explaining.

Provides clear rules and anti-patterns but lacks concrete executable code examples. There's no copy-paste ready snippet showing the correct repeatOnLifecycle pattern or StateFlow collection in a Fragment/Activity, which would significantly improve actionability.

For a relatively simple skill, the rules are clear, but there's no sequenced workflow showing how to set up state collection step-by-step. The anti-patterns section helps but a concrete before/after or step-by-step implementation pattern would improve clarity.

Clean structure with a concise overview and a single well-signaled reference to an implementation template. One level deep, clearly organized sections, and appropriate content split for a skill of this size.