mobile-offline-support
Offline-first mobile apps with local storage, sync queues, conflict resolution. Use for offline functionality, data sync, connectivity handling, or encountering sync conflicts, queue management, storage limits, network transition errors.
96
93%
Does it follow best practices?
Impact
100%
1.36xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a well-crafted skill description that clearly defines its scope around offline-first mobile development patterns. It provides specific capabilities (local storage, sync queues, conflict resolution) and explicit trigger conditions covering both high-level concepts (offline functionality) and specific error scenarios (network transition errors). The description effectively distinguishes itself from general mobile or database skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'local storage, sync queues, conflict resolution' and specific technical concerns like 'queue management, storage limits, network transition errors'. | 3 / 3 |
Completeness | Clearly answers both what ('Offline-first mobile apps with local storage, sync queues, conflict resolution') and when ('Use for offline functionality, data sync, connectivity handling...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'offline functionality', 'data sync', 'connectivity handling', 'sync conflicts', 'network transition errors' - these cover common variations of how users describe offline/sync issues. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on offline-first mobile patterns with distinct triggers like 'sync conflicts', 'queue management', 'network transition errors' - unlikely to conflict with general mobile or storage skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with executable React Native code that covers the core offline-first patterns. The code is well-structured with proper error handling and queue bounds management. The main weakness is the lack of explicit validation/verification steps in the sync workflow, which is important for operations that could result in data loss.
Suggestions
Add explicit validation checkpoint after processQueue() completes, such as verifying synced items match server state or logging sync completion status for debugging
Include a verification step or callback mechanism to confirm successful sync before removing items from the queue permanently
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing executable code without explaining basic concepts Claude already knows. Comments are minimal and purposeful (TODOs for customization, brief explanations of non-obvious logic like queue bounds). | 3 / 3 |
Actionability | Provides fully executable React Native code with proper imports, complete class implementation, and copy-paste ready components. The code includes error handling, queue management, and UI indicators - all concrete and implementable. | 3 / 3 |
Workflow Clarity | The code demonstrates the flow (cache -> queue -> sync) but lacks explicit validation checkpoints. For sync operations that could lose data, there's no explicit verification step after sync completion or guidance on handling partial sync failures beyond retry. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections (Implementation, Conflict Resolution, UI, Best Practices). Appropriately references native implementations in a separate file with clear signaling. Content is appropriately split between overview and detailed reference. | 3 / 3 |
Total | 11 / 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.
- Repository
- secondsky/claude-skills
- Commit
90d6bd7
- 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.