Conciseness

The body is ~40 lines of pure directives ("Expose ONE StateFlow<UiState> via .asStateFlow()", "Use SharingStarted.WhileSubscribed(5000)") with zero concept explanation, no padding, and no restating of what Claude already knows about coroutines or Compose. Every token earns its place, matching the 5 anchor.

Actionability

Concrete, executable specifics are given throughout (`.asStateFlow()`, `viewModelScope`, `collectAsStateWithLifecycle()`, `@Immutable`, `./gradlew test`) and full copy-paste Kotlin templates live in references/implementation.md. It stops short of the 5 anchor because the body itself contains no inline code example — all runnable code is deferred to the reference file — leaving minor gaps if the reference isn't opened.

Workflow Clarity

A clear numbered sequence (1. Structure ViewModel → 2. Define UI State → 3. Collect State) is followed by an explicit Verification checklist including a runnable command ("./gradlew test passes for ViewModel tests"), which satisfies the validation-checkpoint expectation. There is no error-recovery feedback loop (what to do when a checklist item fails), so it matches the 4 anchor rather than the 5.

Progressive Disclosure

The body is a lean overview with well-labeled sections and a single one-level-deep reference (references/implementation.md, verified to exist and contain the actual templates) linked from both relevant sections and a References list. No nesting, no buried references, no inlined content that belongs elsewhere — a clean match for the 5 anchor.

Specificity

"Configure ViewModel state emission with StateFlow, SharedFlow, and sealed UiState classes in Android" names the domain and several concrete technologies/actions (state emission, state modeling, sharing policies), with only minor coverage gaps (e.g., no mention of specific collection or migration actions). It falls just short of the 5 anchor's comprehensive multi-action list, and well above the 3 anchor's 1-2 concrete actions.

Completeness

Both parts are present: a clear 'what' ("Configure ViewModel state emission with StateFlow, SharedFlow, and sealed UiState classes") and an explicit 'when' ("Use for state modeling and sharing policies"). The 'when' clause is explicit but abstract — no concrete user-side trigger phrases like "when the user mentions StateFlow or UiState" — so it matches the 4 anchor, not the 5.

Trigger Term Quality

Natural Android terms users would say are present: "ViewModel", "StateFlow", "UiState", "Hilt injection", "navigation-event plumbing". A few natural synonyms a user might say (e.g., "UI state", "Android state management", "LiveData migration") are missing, matching the 4 anchor rather than the comprehensive 5 anchor.

Distinctiveness Conflict Risk

The description carves out a clear niche (ViewModel state emission policy) and explicitly defers adjacent concerns — "generic lifecycle collection, navigation-event plumbing, Hilt injection, test code, and configuration-change recipes to their specific skills" — minimizing conflict risk with sibling skills, matching the 5 anchor's clear niche with distinct triggers.