CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/mobile-offline-support/skills/mobile-offline-support/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured with executable React Native code and an appropriately split native-implementations reference, but placeholder API implementations and missing validation checkpoints for batch sync operations limit actionability and workflow clarity.

Suggestions

Add an explicit validation/verification step to the sync workflow (e.g., verify queue items persisted before clearing, or validate conflict-resolution results), since batch sync operations cap workflow clarity at 3 without one.

Remove the placeholder TODO comments in fetchFromServer/syncToServer by either defining API_BASE_URL or clearly marking the functions as adapters the user must wire up, and delete the unreachable merge code after the early return in resolveConflict.

Tighten verbose comments like 'Example implementation - replace with your API' and 'Enforce queue bounds - discard oldest if exceeded' to assume Claude's competence and reduce token weight.

DimensionReasoningScore

Conciseness

The body is mostly lean executable code with brief section headers and concise bullet lists, but contains a few over-explanatory TODO comments ('Example implementation - replace with your API') that could be trimmed.

4 / 5

Actionability

Provides mostly executable, concrete code for the OfflineManager, UI indicator, and conflict resolution, but has minor gaps: undefined API_BASE_URL and styles, placeholder TODO implementations, and unreachable code after the early return in resolveConflict.

4 / 5

Workflow Clarity

The skill involves batch sync-queue processing and conflict resolution but lacks explicit validation or verification checkpoints, so workflow clarity is capped at 3 per the destructive/batch-operation guideline.

3 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled one-level-deep reference to the real references/native-implementations.md file, whose contents (iOS Core Data, Android Room) are described inline for easy navigation.

5 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 is strong, clearly answering both what the skill does and when to use it with concrete trigger phrases and a distinct mobile-offline niche. The only minor weakness is that capabilities are phrased as feature nouns rather than concrete verb-actions.

DimensionReasoningScore

Specificity

Names the domain ('Offline-first mobile apps') and lists several concrete capability areas ('local storage, sync queues, conflict resolution'), though these are feature nouns rather than verb-actions, leaving minor coverage gaps.

4 / 5

Completeness

Clearly states what the skill does and provides an explicit 'Use for ...' trigger clause enumerating concrete trigger phrases, satisfying both what and when.

5 / 5

Trigger Term Quality

Good coverage of natural user phrases ('offline functionality', 'data sync', 'sync conflicts', 'connectivity handling'), with only a few synonyms missing and the slightly technical 'network transition errors' term.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (offline-first mobile apps) with distinct triggers (offline sync, conflict resolution, connectivity) and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
secondsky/claude-skills
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.