Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rshankras/offline-queue
Generates an offline operation queue with persistence, automatic retry on connectivity, and conflict resolution.
Passed 19 of 22 test cases with the skill, and 14 of 22 without it.
and 2 more in the full report
5 fixed14 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
In a Swift project root that contains neither a `Sources/` nor an `App/` directory, into which output folder should offline queue files be generated?
| Checked | Without skill | With skill |
|---|---|---|
| Place generated files in a top-level `OfflineQueue/` directory | Missed | Passed |
The instructions your model reads when the skill loads.
Generate a production offline operation queue that persists API requests/mutations when offline, stores them to disk, and retries with exponential backoff when connectivity returns. Essential for apps that need offline-first behavior.
Use this skill when the user:
Search for existing networking/offline code:
Glob: **/*OfflineQueue*.swift, **/*OfflineOperation*.swift, **/*NetworkMonitor*.swift, **/*RetryPolicy*.swift
Grep: "NWPathMonitor" or "OfflineQueue" or "pendingOperations" or "offlineQueue"
If existing offline handling found:
Check for Network framework availability (required for NWPathMonitor). Available on iOS 12+ / macOS 10.14+, so effectively always available for our iOS 16+ / macOS 13+ targets.
Ask user via AskUserQuestion:
test cases passed, vs 14 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.