CtrlK
BlogDocsLog inGet started
Tessl Logo

android-persistence

Implement Room database schemas and DataStore preferences with proper async patterns in Android. Use when defining Room entities, DAOs, migrations, or replacing SharedPreferences with DataStore.

69

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A tight, well-organized standards skill that delegates executable Kotlin to a real one-level-deep reference file. Its main gaps are the absence of inline executable examples and missing validation/feedback loops for risky database operations like migrations.

Suggestions

Add one compact inline DAO/DataStore code snippet so the body is copy-paste ready without opening the reference.

Insert a validation checkpoint for migrations (e.g. test the schema/export, verify Migration objects cover version jumps) and a fix-and-retry loop.

Note how to verify Flow collection runs off the Main thread rather than only stating the anti-pattern.

DimensionReasoningScore

Conciseness

Lean bullet standards with no padding and no explanation of concepts Claude already knows; every directive earns its place.

3 / 3

Actionability

Directives name concrete APIs ("Flow<List<T>>", "suspend", "@Transaction", "ProtoDataStore", Hilt) but the body itself has no inline executable code, deferring copy-paste examples to the reference file.

2 / 3

Workflow Clarity

Standards are grouped into clear sections, but there are no validation/verification checkpoints for migrations or schema changes, and the rubric caps database-context workflow clarity at 2 without feedback loops.

2 / 3

Progressive Disclosure

A concise overview with well-signaled, one-level-deep references to the verified references/implementation.md file; content is appropriately split and easy to navigate.

3 / 3

Total

10

/

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 names concrete capabilities and pairs them with an explicit "Use when" trigger clause covering natural developer terms. It cleanly answers what the skill does and when to invoke it with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Implement Room database schemas", "DataStore preferences", "proper async patterns" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Implement Room database schemas and DataStore preferences...") and when via a clear "Use when..." clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

Covers natural terms an Android developer would say — "Room entities, DAOs, migrations", "SharedPreferences", "DataStore" — in third-person voice.

3 / 3

Distinctiveness Conflict Risk

Targets a clear Android-persistence niche with distinct Room/DataStore triggers that are unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.