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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill mobile-offline-support84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 its scope around offline-first mobile development patterns. It effectively combines specific technical capabilities with natural trigger terms users would use when encountering sync and connectivity issues. The explicit 'Use for...' clause provides clear guidance on when to select this skill.
| 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
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, actionable React Native code for offline-first mobile apps with good structure and appropriate progressive disclosure. The main weaknesses are some verbosity in the code comments and missing explicit validation/verification steps for the sync workflow, particularly around conflict resolution and error recovery.
Suggestions
Add explicit validation checkpoint after processQueue() completes (e.g., verify sync count, log success/failure summary)
Expand conflict resolution section with a concrete workflow: detect conflict -> present options -> resolve -> verify
Trim TODO comments and error logging boilerplate - Claude can infer these patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The code is mostly efficient but includes some unnecessary verbosity like extensive TODO comments and error handling boilerplate that Claude could infer. The best practices and avoid sections add value but could be more condensed. | 2 / 3 |
Actionability | Provides fully executable React Native code with complete class implementation, conflict resolution function, and UI component. Code is copy-paste ready with clear imports and realistic patterns. | 3 / 3 |
Workflow Clarity | The code demonstrates the flow (cache -> queue -> sync) but lacks explicit validation checkpoints. Missing guidance on verifying sync success, handling partial failures, or recovery steps when conflicts occur. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections (implementation, conflict resolution, UI, best practices) and appropriate reference to native implementations in a separate file. One-level-deep reference is clearly signaled. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.