android-legacy-state

Integrate ViewModel state with XML Views using Coroutines and Lifecycle on Android. Use when managing state with repeatOnLifecycle or lifecycle-aware coroutines in Fragment/Activity; defer Compose state and generic Flow design to their specific skills.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-5

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

A tight, well-structured standards skill that respects token budget, gives concrete actionable rules, and cleanly offloads detail to a verified reference file. Actionability is the only slightly-less-than-max dimension because some guidance is rule-style rather than inline copy-paste code.

Dimension	Reasoning	Score
Conciseness	The ~22-line body is lean and assumes Claude's competence, with no padding or explanation of basic concepts like coroutines or the Lifecycle library.	5 / 5
Actionability	Provides concrete rules ('ALWAYS use repeatOnLifecycle(Lifecycle.State.STARTED)', 'observe with viewLifecycleOwner') and executable code in the reference file, though some guidance is rule-based rather than copy-paste ready inline.	4 / 5
Workflow Clarity	As a single-purpose standards skill with no destructive or batch operations, the guidance is unambiguous; the simple-skill exception applies.	5 / 5
Progressive Disclosure	The body is a concise overview with clear section headers and a single well-signaled one-level-deep reference to references/implementation.md, which exists as a real bundle file.	5 / 5
	Total	19 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 well-crafted description that clearly states capabilities and explicit trigger conditions while actively de-scoping adjacent skills. Minor gaps in keyword synonym coverage keep specificity and trigger quality just below maximum.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('Integrate ViewModel state with XML Views', 'managing state with repeatOnLifecycle or lifecycle-aware coroutines') plus an explicit boundary, but stops short of fully comprehensive coverage.	4 / 5
Completeness	Explicitly answers both 'what' ('Integrate ViewModel state with XML Views...') and 'when' ('Use when managing state with repeatOnLifecycle or lifecycle-aware coroutines in Fragment/Activity') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes several natural developer-facing terms ('repeatOnLifecycle', 'lifecycle-aware coroutines', 'Fragment/Activity', 'launchWhenStarted') but is missing some common synonyms or extensions.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche by explicitly deferring adjacent concerns ('defer Compose state and generic Flow design to their specific skills'), minimizing conflict risk with sibling skills.	5 / 5
	Total	18 / 20 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
Path: skills/android/android-legacy-state/SKILL.md
Commit: 405cdd5

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.