android-state

Configure ViewModel state emission with StateFlow, sealed UiState classes, and lifecycle-safe collection in Android. Use when working with ViewModels, UiState patterns, or exposing state to Compose UI.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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

A well-structured, token-efficient skill body that gives specific actionable API guidance, a clear sequenced workflow with a verification checklist, and a single well-signaled reference file holding executable templates. It respects Claude's competence while remaining concrete.

Dimension	Reasoning	Score
Conciseness	Lean bullet-point body with no concept re-explanation or padding — 'Expose ONE StateFlow<UiState> via .asStateFlow()' assumes Claude's competence and every token earns its place.	3 / 3
Actionability	Provides concrete, specific API directives — .asStateFlow(), viewModelScope, collectAsStateWithLifecycle(), SharingStarted.WhileSubscribed(5000) — with copy-paste-ready Kotlin templates one level deep in references/implementation.md; guidance is actionable rather than abstract.	3 / 3
Workflow Clarity	Sequenced sections (Structure ViewModel → Define UI State → Collect State) plus an explicit Verification checklist including './gradlew test', giving a clear sequence with a validation checkpoint.	3 / 3
Progressive Disclosure	Concise overview body with a single, clearly signaled one-level-deep reference — 'See [templates](references/implementation.md)' — pointing to a real file containing the detailed templates; navigation is easy and content is appropriately split.	3 / 3
	Total	12 / 12 Passed

Description

100%

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 concise, third-person description that explicitly covers what the skill does and when to use it, with concrete capabilities and natural trigger terms. It avoids fluff and over-claims while remaining clearly distinguishable from other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Configure ViewModel state emission with StateFlow, sealed UiState classes, and lifecycle-safe collection' — naming three distinct, specific capabilities rather than vague language.	3 / 3
Completeness	Clearly answers both what (configure state emission with StateFlow/sealed UiState/lifecycle-safe collection) and when via an explicit 'Use when working with ViewModels, UiState patterns, or exposing state to Compose UI' clause.	3 / 3
Trigger Term Quality	The 'Use when' clause names natural developer terms — 'ViewModels, UiState patterns, or exposing state to Compose UI' — that a user would actually say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Scoped to Android ViewModel/StateFlow/Compose state with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Commit: 611f52a

Reviewed: 4 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.