android-legacy-state

Integrate ViewModel state with Views using Coroutines and Lifecycle on Android. Use when managing state with repeatOnLifecycle or lifecycle-aware coroutines in Fragment/Activity.

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 compact, well-structured standards skill that delivers exact API-level rules and anti-patterns without padding, offloading the executable template to a single real reference file. It exemplifies token-efficient, actionable guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean: terse rules with brief, earned 'Why' notes and no explanation of basic Android/lifecycle concepts Claude already knows.	3 / 3
Actionability	Rules cite exact APIs ('repeatOnLifecycle(Lifecycle.State.STARTED)', 'StateFlow', 'viewLifecycleOwner', NOT 'this') and exact anti-patterns ('launchWhenStarted/Resumed', 'observe(this)'); per the instruction-only carve-out, absence of inline code is not penalized when guidance is this actionable, and a full template lives in the referenced file.	3 / 3
Workflow Clarity	This is a single-purpose standards skill with unambiguous directives and no destructive multi-step operation requiring validation checkpoints, so the simple-skill carve-out applies.	3 / 3
Progressive Disclosure	Under 50 lines, well-organized into Implementation Guidelines / Anti-Patterns / References, with a single one-level-deep reference to references/implementation.md that exists and holds the code template.	3 / 3
	Total	12 / 12 Passed

Description

90%

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, well-targeted description that clearly states both capability and trigger conditions using natural Android vocabulary. Its only weakness is that it names a single integrating action rather than a list of concrete actions.

Suggestions

Expand the capability clause to list concrete actions (e.g., 'collect flows, migrate LiveData to StateFlow, and fix lifecycle leaks') to lift specificity to a 3.

Dimension	Reasoning	Score
Specificity	Names the domain ('Integrate ViewModel state with Views using Coroutines and Lifecycle on Android') and one concrete action, but does not enumerate multiple specific actions; it is not comprehensive enough for a 3.	2 / 3
Completeness	It explicitly answers both what (integrate ViewModel state with Views) and when ('Use when managing state with repeatOnLifecycle or lifecycle-aware coroutines in Fragment/Activity').	3 / 3
Trigger Term Quality	'repeatOnLifecycle', 'lifecycle-aware coroutines', and 'Fragment/Activity' are natural terms an Android developer would say when reaching for this skill.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow (Android legacy state, repeatOnLifecycle, lifecycle-aware coroutines) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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.