agentsclimarketplace

Android room database

Skill krutikJain/android-agent-skills/.github/skills/android-room-database

Android skills repository for Kotlin, Compose, XML, testing, CI, release work, and legacy upgrades

Install
npx -y skills add krutikJain/android-agent-skills --skill android-room-database

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Model Room entities, DAOs, transactions, migrations, schema exports, and test-safe local persistence.

SKILL.md

4.5 KB, 781 tokens by cl100k_base, as published. Nobody here has run it

Android Room Database

When To Use

  • Use this skill when the request is about: room database android, dao query migration android, room schema export.
  • Primary outcome: Model Room entities, DAOs, transactions, migrations, schema exports, and test-safe local persistence.
  • Reach for this skill when the hard part is schema design, DAO queries, transactions, migrations, or Room testing. Hand off to android-rxjava-to-coroutines-migration only if the main work is reactive API migration rather than the database contract itself.
  • Handoff skills when the scope expands:
  • android-local-persistence-datastore
  • android-testing-unit

Workflow

  1. Start with the persistence contract: entities, keys, indexes, relations, and whether the data is source-of-truth, cache, or offline-first state.
  2. Model DAO access patterns explicitly, including transaction boundaries, query shape, paging, and invalidation behavior.
  3. Plan schema evolution before changing entities: exported schemas, migration steps, auto-migration eligibility, and destructive-fallback policy.
  4. Validate migration and query behavior with deterministic tests rather than assuming Room annotations are enough.
  5. Hand off DataStore, sync, or reactive API questions only after the Room boundary is correct.

Guardrails

  • Export schemas and treat them as part of the contract, not optional tooling noise.
  • Keep entities persistence-focused; map to domain/UI models instead of leaking table shape upward.
  • Use explicit transactions for multi-step writes that must remain consistent.
  • Test migrations against real old schemas before trusting them in release builds.

Anti-Patterns

  • Treating Room entities as the app's domain model everywhere.
  • Editing schemas without exporting or validating migration paths.
  • Writing broad SELECT * queries when the screen only needs a narrow projection.
  • Collapsing database, sync, and reactive-stream migration problems into one undifferentiated task.

Review Focus

  • Entity keys, indexes, relations, and schema ownership.
  • DAO query shape, transactions, and invalidation behavior.
  • Migration safety, schema exports, and test coverage.
  • Clear boundaries between Room models and higher-level app models.

Examples

Happy path

  • Scenario: Persist task items and reminder flags with schema-aware entities.
  • Command: cd examples/orbittasks-compose && ./gradlew :app:testDebugUnitTest

Edge case

  • Scenario: Recover from a failed schema change with an explicit migration path.
  • Command: python3 scripts/eval_triggers.py --skill android-room-database

Failure recovery

  • Scenario: Keep Room requests separate from DataStore, networking, and modernization prompts.
  • Command: cd examples/orbittasks-xml && ./gradlew :app:testDebugUnitTest

Done Checklist

  • Entities, DAOs, and transactions match the real persistence contract.
  • Schema export and migration strategy are explicit.
  • Query and migration tests cover the risky paths.
  • Non-Room concerns are handed off instead of mixed into the database task.

Official References

Gives 0 of the 12 instructions most databases sql skills give in 781 tokens

Counted across 589 of the 662 authors here whose files we hold, read 2026-08-06

  • use parameterized queriesin 36 of 589, across 32 files
  • use timestamptz for timestampsin 30 of 589, across 12 files
  • create indexes concurrentlyin 29 of 589, across 23 files
  • index foreign keysin 28 of 589, across 17 files
  • use numeric type for moneyin 25 of 589, across 8 files
  • select only required columnsin 24 of 589, across 19 files
  • use cursor pagination instead of OFFSETin 23 of 589, across 15 files
  • add indexes manually on foreign key columnsin 22 of 589, across 11 files
  • read individual rule files for detailed explanationsin 18 of 589, across 4 files
  • configure connection poolingin 18 of 589, across 16 files
  • put equality columns before range columns in indexesin 17 of 589, across 9 files
  • normalize to third normal formin 17 of 589, across 8 files

Said here and by no other author read

  • export schemas and treat them as contractual
  • keep entities persistence-focused
  • map to domain models instead of leaking table shapes
  • test migrations against real old schemas
  • validate migration and query behavior with tests
  • hand off non-room concerns to other skills

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.