Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rshankras/lapsed-user
Generates lapsed user detection and re-engagement screens with personalized return experiences, win-back offers, and inactivity tracking.
Passed 18 of 22 test cases with the skill, and 8 of 22 without it.
and 12 more in the full report
10 fixed8 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
If our codebase already has an `AnalyticsTracker.swift` storing `lastActiveDate` in `UserDefaults`, what step should be taken before generating a standalone storage mechanism?
| Checked | Without skill | With skill |
|---|---|---|
| Asks the user whether to integrate with existing engagement tracking. | Missed | Passed |
The instructions your model reads when the skill loads.
Generate production infrastructure for detecting users who haven't opened the app in X days, showing personalized return screens that highlight what they missed, and optionally presenting win-back incentives to recover churned or lapsing users.
Use this skill when the user:
Search for existing engagement or analytics infrastructure:
Glob: **/*Analytics*.swift, **/*Engagement*.swift, **/*Tracker*.swift, **/*Activity*.swift
Grep: "lastActiveDate" or "UserDefaults" or "scenePhase" or "applicationDidBecomeActive"
If existing tracking found:
Search for existing push notification configuration:
Glob: **/*Notification*.swift, **/*Push*.swift
Grep: "UNUserNotificationCenter" or "UNNotification" or "registerForRemoteNotifications"
If push notifications are configured, offer push-based re-engagement as an option.
test cases passed, vs 8 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.