android-data-layer
Guidance on implementing the Data Layer using Repository pattern, Room (Local), and Retrofit (Remote) with offline-first synchronization.
59
48%
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 ./.github/skills/android-data-layer/SKILL.mdQuality
Discovery
32%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 identifies a specific technical domain (Android Data Layer architecture) with named technologies, providing moderate specificity. However, it lacks concrete actions, misses a 'Use when...' clause entirely, and reads more like a topic label than actionable guidance for skill selection.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when implementing Android data persistence, setting up offline-first architecture, or configuring Room with Retrofit'.
List concrete actions the skill enables, such as 'Create repository classes, configure Room DAOs, set up Retrofit services, implement cache invalidation strategies'.
Include common user phrases and variations like 'local database', 'API caching', 'Android persistence', 'sync data', or 'offline mode'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Data Layer) and specific technologies (Repository pattern, Room, Retrofit) with a concept (offline-first synchronization), but doesn't list concrete actions like 'create repositories', 'configure caching', or 'handle sync conflicts'. | 2 / 3 |
Completeness | Describes what the skill covers (Data Layer implementation guidance) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical keywords (Repository pattern, Room, Retrofit, offline-first) that developers would use, but misses common variations like 'local database', 'API calls', 'caching', 'Android persistence', or 'data sync'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Repository pattern + Room + Retrofit + offline-first is fairly specific to Android development, but 'Data Layer' and 'synchronization' are generic enough to potentially overlap with other data-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%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 solid, concise overview of Android Data Layer architecture with good code examples for the core Repository pattern. However, it falls short on complete actionability for Room/Retrofit setup and lacks explicit workflow steps with validation for synchronization operations. The content would benefit from more executable examples and clearer step-by-step sync workflows.
Suggestions
Add complete, executable code examples for Room Entity/DAO definitions and Retrofit interface setup
Expand the Synchronization section with explicit numbered steps and error handling/retry logic for both read and write flows
Include a concrete WorkManager implementation example for the Outbox Pattern rather than just describing it conceptually
Consider splitting advanced sync patterns into a referenced SYNC_PATTERNS.md file with detailed implementations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using bullet points and minimal prose. It assumes Claude understands Android development concepts like Hilt, Flow, and suspend functions without explaining them. | 3 / 3 |
Actionability | Provides executable Kotlin code for Repository pattern and DI binding, but Room Entity/DAO and Retrofit interface examples are described rather than shown. The sync patterns mention concepts without complete implementation examples. | 2 / 3 |
Workflow Clarity | The read/write sync patterns are described conceptually but lack explicit step-by-step sequences. No validation checkpoints for error recovery in the sync workflow, and the Outbox Pattern is marked 'Advanced' without concrete implementation steps. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. Advanced topics like Outbox Pattern could benefit from references to separate detailed guides. No external file references for deeper dives. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
3f68e39
- 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.