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.
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 strong skill description that clearly defines a specific niche (offline-first mobile development) with concrete capabilities and explicit trigger conditions. It uses third-person voice appropriately and includes a comprehensive set of natural trigger terms covering both the core functionality and common error scenarios developers would encounter.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions/capabilities: local storage, sync queues, conflict resolution, connectivity handling, queue management, storage limits, and network transition errors. | 3 / 3 |
Completeness | Clearly answers both 'what' (offline-first mobile apps with local storage, sync queues, conflict resolution) and 'when' (explicit 'Use for' clause listing offline functionality, data sync, connectivity handling, and specific error scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'offline', 'sync', 'conflict resolution', 'data sync', 'connectivity', 'queue management', 'storage limits', 'network transition errors'. These cover a good range of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'offline-first mobile apps' with sync queues, conflict resolution, and network transition errors creates a very distinct niche that is unlikely to conflict with general mobile development or general data storage skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, executable React Native code for offline-first mobile apps with good progressive disclosure to native implementations. However, it includes some unnecessary boilerplate (fetchFromServer/syncToServer stubs, generic best practices) that Claude could generate independently, and it lacks explicit workflow sequencing with validation checkpoints for the sync process, which is a potentially destructive/lossy operation.
Suggestions
Remove the fetchFromServer and syncToServer stub implementations and replace with brief comments indicating these are API-specific; Claude can generate appropriate fetch code.
Remove or significantly trim the 'Best Practices' and 'Avoid' sections - these are generic advice Claude already knows.
Add an explicit workflow section with numbered steps for implementing offline support in a new app, including validation checkpoints (e.g., verify queue persistence, test conflict resolution, validate data integrity after sync).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The code is mostly useful but includes some unnecessary verbosity - the fetchFromServer and syncToServer methods with TODO comments and full error handling boilerplate are filler that Claude could generate on its own. The best practices and avoid sections are generic advice Claude already knows. | 2 / 3 |
Actionability | The skill provides fully executable code examples for the OfflineManager class, conflict resolution, and UI indicator component. The code is copy-paste ready with concrete implementations using real libraries (AsyncStorage, NetInfo). | 3 / 3 |
Workflow Clarity | The skill shows the components of an offline-first system but lacks explicit workflow sequencing for integration. There are no validation checkpoints - e.g., no guidance on verifying sync queue integrity after recovery, testing conflict resolution outcomes, or handling the transition from offline to online gracefully with verification steps. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with the core React Native implementation inline and appropriately defers native iOS/Android implementations to a separate reference file with clear signaling. The structure is well-organized with logical sections. | 3 / 3 |
Total | 10 / 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
88da5ff
- 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.