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.
92
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that clearly defines a specific Android development pattern, includes natural trigger terms that developers would use, and explicitly states both what the skill does and when to use it. The description is concise yet comprehensive, covering the key technologies and use cases without unnecessary verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure ViewModel state emission with StateFlow, sealed UiState classes, and lifecycle-safe collection in Android.' This names specific technologies (StateFlow, sealed UiState classes) and concrete patterns (lifecycle-safe collection). | 3 / 3 |
Completeness | Clearly answers both 'what' (configure ViewModel state emission with StateFlow, sealed UiState classes, lifecycle-safe collection) and 'when' (explicit 'Use when working with ViewModels, UiState patterns, or exposing state to Compose UI'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords a developer would use: 'ViewModel', 'StateFlow', 'UiState', 'sealed', 'lifecycle-safe', 'Compose UI', 'state emission'. These are terms Android developers naturally use when seeking help with this pattern. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Android ViewModel state management with StateFlow and Compose UI. The combination of ViewModel, StateFlow, sealed UiState, and lifecycle-safe collection creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that clearly sequences the Android state management workflow with good validation checkpoints and appropriate progressive disclosure. Its main weakness is that actionable code examples are entirely delegated to a reference file, meaning the skill body itself lacks executable, copy-paste ready snippets that would make it immediately actionable without navigating to the reference.
Suggestions
Add at least one minimal inline code example (e.g., a 5-line ViewModel skeleton with StateFlow) so the skill is actionable without requiring the reference file.
Include a brief inline sealed interface example (3-4 lines) for the UiState pattern to make Section 2 immediately executable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line is purposeful and assumes Claude knows Android/Kotlin fundamentals. No unnecessary explanations of what StateFlow or ViewModels are. Bullet points are tight and directive. | 3 / 3 |
Actionability | The guidance is specific (e.g., use `.asStateFlow()`, `collectAsStateWithLifecycle()`, `SharingStarted.WhileSubscribed(5000)`) but lacks inline executable code examples—actual templates are deferred to a reference file. Without seeing those templates, the skill itself doesn't provide copy-paste ready code. | 2 / 3 |
Workflow Clarity | The numbered steps provide a clear sequence (structure ViewModel → define UiState → collect state), anti-patterns serve as guardrails, and the verification checklist provides explicit validation checkpoints including a test command. | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with well-signaled, one-level-deep references to `references/implementation.md` for detailed templates. Content is appropriately split between the overview and reference material. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
4c72e76
- Reviewed
Table of Contents
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.