android-persistence

Implement Room schemas and DataStore preferences with proper async patterns in Android. Use when the primary task is storage schema, DAO, migration, or preference isolation; defer auth-token/security storage, any CoroutineWorker/WorkManager task, Hilt graph wiring, and cache-policy design.

Quality

93%

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

87%Weight 40%Scale 1-3

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

A concise, well-structured overview that delegates executable detail to a real one-level-deep reference file. The only gap is workflow clarity: the DataStore migration and Room setup lack explicit validation/verification checkpoints that database operations warrant.

Suggestions

Add a verification step to the DataStore migration (e.g., read the migrated value back via the Flow and assert it matches the old SharedPreferences state) so the workflow has a feedback loop.

Frame the two sections as a sequenced process or add a short validation checkpoint after Room configuration (e.g., compile/build check or schema export verification) to lift workflow clarity above 2.

Fix the repeated link label: the DataStore section points to references/implementation.md as "DAO templates", which is inaccurate — relabel it to reflect the DataStore content in that file.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet-pointed guidance with no padding and no explanation of concepts Claude already knows (e.g., what Room is), so every token earns its place rather than being verbose.	3 / 3
Actionability	Guidance names concrete, specific APIs ("Flow<List<T>>", "suspend", "@Transaction", "ProtoDataStore"/"PreferencesDataStore", Hilt singleton) with executable code one level deep in references/implementation.md; per the instruction-only scoring note, actionable specific guidance is not penalized for lacking inline code.	3 / 3
Workflow Clarity	The two numbered sections are organized but are parallel topic areas rather than a sequenced process, and neither the Room setup nor the DataStore migration includes a validation/verification checkpoint — database/migration operations should cap at 2 per the feedback-loops note, so it is not a 3.	2 / 3
Progressive Disclosure	The SKILL.md body is a concise overview pointing to a single one-level-deep, clearly signaled reference (references/implementation.md, verified to exist with the detailed code), matching the clear-overview-with-well-signaled-references anchor.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 strong description: third-person/imperative voice, concrete capabilities, explicit Use-when triggers, and an explicit deferral carve-out that minimizes conflict with sibling skills. All four dimensions land at the top anchor.

Dimension	Reasoning	Score
Specificity	"Implement Room schemas and DataStore preferences with proper async patterns" lists multiple concrete actions (Room schemas, DataStore preferences, async patterns), matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	It answers both what ("Implement Room schemas and DataStore preferences...") and when ("Use when the primary task is storage schema, DAO, migration, or preference isolation"), with an explicit Use-when clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	Natural Android-persistence terms a developer would say appear throughout — "Room", "DataStore", "DAO", "migration", "SharedPreferences" — giving good coverage rather than only some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	The explicit deferral list ("defer auth-token/security storage, any CoroutineWorker/WorkManager task, Hilt graph wiring, and cache-policy design") carves out a clear niche and actively avoids overlap with adjacent 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
Path: skills/android/android-persistence/SKILL.md
Commit: 9f695e8

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