android-room-database
Model Room entities, DAOs, transactions, migrations, schema exports, and test-safe local persistence.
53
42%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/android-room-database/SKILL.mdQuality
Discovery
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description does well at listing specific Room-related capabilities and occupies a clear niche, making it distinctive. However, it critically lacks any 'Use when...' guidance, which would help Claude know when to select this skill. It also misses broader natural language trigger terms like 'Android database' or 'SQLite' that users might commonly use.
Suggestions
Add a 'Use when...' clause such as 'Use when the user needs to set up or modify Android Room database components, local persistence, or SQLite-backed storage.'
Include broader natural trigger terms like 'Android database', 'SQLite', 'local database', 'offline storage', or 'persistence layer' to capture common user phrasing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: entities, DAOs, transactions, migrations, schema exports, and test-safe local persistence. These are all distinct, concrete capabilities within the Room domain. | 3 / 3 |
Completeness | Describes what the skill does (model Room entities, DAOs, etc.) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Room', 'entities', 'DAOs', 'migrations', and 'schema exports' that users familiar with Android development would use. However, it misses common natural variations like 'Android database', 'SQLite', 'local database', '@Entity', '@Dao', or '.db' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Android Room persistence library, which is a distinct niche. Terms like 'Room entities', 'DAOs', 'schema exports' are highly specific and unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-organized conceptual framework for working with Android Room databases, with clear workflow sequencing and good guardrails/anti-patterns. However, it critically lacks any concrete code examples—no entity definitions, DAO interfaces, migration implementations, or test snippets—making it more of a checklist than an actionable skill. The content would benefit significantly from executable Kotlin examples demonstrating the key patterns it describes.
Suggestions
Add concrete, executable Kotlin code examples for at least: an @Entity definition with keys/indexes, a @Dao interface with typed queries and a @Transaction method, and a Migration implementation.
Include a concrete schema export configuration snippet (e.g., the room { schemaLocation } block in build.gradle) since this is emphasized as critical but never shown.
Add a concrete Room test example using MigrationTestHelper or an in-memory database setup, since testing is a core part of the workflow.
Consider linking to or creating companion files for detailed migration patterns and DAO query patterns to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient and avoids explaining what Room is to Claude, but sections like 'When To Use' and 'Review Focus' overlap significantly with the 'Workflow' and 'Done Checklist' sections, creating redundancy. The guardrails and anti-patterns sections also partially restate each other. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete Room entity/DAO examples, no migration code snippets, and no schema export configuration. It describes what to do at a high conceptual level but never shows how—there are no copy-paste ready Kotlin/Java snippets for entities, DAOs, migrations, or test setups. | 1 / 3 |
Workflow Clarity | The workflow has a clear 5-step sequence covering schema design through handoff, and step 4 mentions validation via tests. However, the validation steps are abstract ('validate migration and query behavior with deterministic tests') rather than concrete commands or explicit checkpoints with feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and mentions handoff skills, but it doesn't reference any deeper companion files (e.g., a detailed migration guide, DAO patterns reference, or examples file). The examples section provides commands but no linked detailed documentation. For a skill of this complexity, more progressive disclosure to detailed materials would be expected. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- krutikJain/android-agent-skills
- Commit
c5bf673
- 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.