You optimize every stage of the subscription journey: trial → paid → renewal → cancellation recovery → win-back.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsubscription-lifecycleExecute the skills CLI command in your project's root directory to begin installation:
Fetches subscription-lifecycle from eronred/aso-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate subscription-lifecycle. Access via /subscription-lifecycle in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
696
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
696
stars
You optimize every stage of the subscription journey: trial → paid → renewal → cancellation recovery → win-back.
Install → Trial start → [Trial period] → Conversion → Renewal → ... → Cancel → Win-back
↓ ↓ ↓ ↓
No convert Voluntary Involuntary Lapsed
(nurture) (exit survey) (dunning) (campaign)
| Stage | Metric | Formula | Benchmark |
|---|---|---|---|
| Trial | Trial start rate | Trials / Downloads | > 20% |
| Trial | Trial-to-paid | Conversions / Trials | 25–40% strong |
| Retention | Month 1 renewal | M1 renewals / Subscribers | > 70% |
| Retention | Month 6 renewal | M6 renewals / Subscribers | > 50% |
| Churn | Monthly churn | Lost subs / Start subs | < 5% good; < 2% excellent |
| Revenue | MRR | Active subs × monthly price | — |
| Revenue | LTV | ARPU / Monthly churn rate | — |
| Recovery | Dunning recovery | Recovered / Failed payments | > 30% |
| Win-back | Resubscribe rate | Returns / Lapsed | 5–15% |
| App Type | Recommended trial | Notes |
|---|---|---|
| Simple utility | 3–7 days | Value obvious quickly |
| Health/fitness | 7–14 days | Habit formation needs time |
| Productivity | 7–14 days | Workflow integration |
| Education | 7–14 days | First lesson completion |
| Entertainment | 7 days | Binge behavior |
Test: Monthly apps with a 7-day trial vs. 14-day trial — conversion rate may drop slightly but LTV often increases.
Send in-app (or push) messages during the trial to drive activation:
Day 0: Welcome — "Your trial has started. Here's how to get the most from it."
Day 1: Core feature highlight — "Try [key feature] today"
Day 3: Progress / social proof — "Users who do X get 3× better results"
Day 5 (7-day trial): Urgency — "2 days left in your trial"
Day 6: Value recap — "Here's what you've done / could do with premium"
Day 7: Last day — "Your trial ends today"
Rule: Messages should show value, not just create pressure.
At trial end, show a paywall that:
See monetization-strategy for paywall design details.
| Reason | Signal | Fix |
|---|---|---|
| Forgot they subscribed | Low sessions, no activation | Improve onboarding + notification strategy |
| Not enough value | Low feature usage | Push underused high-value features |
| Too expensive | Price sensitivity | Introduce lower-tier or pause option |
| Problem with app | 1-star reviews | Fix the bug, reply to reviews |
| Found alternative | — | Monitor competitor installs |
| Seasonal use | Churns at same time yearly | Offer a pause option |
When a user initiates cancellation (iOS — ManagedSubscriptionGroup):
Cancellation exit survey options:
Users at high churn risk:
Trigger a re-engagement push or in-app message before they cancel.
Involuntary churn accounts for 20–40% of all subscription cancellations.
| Day | Action |
|---|---|
| 0 | Payment fails silently — Apple/Google retry |
| 3 | Apple/Google retry #2 |
| 7 | Apple/Google retry #3 — show in-app "Update payment method" banner |
| 10 | Send push: "Your subscription couldn't be renewed — tap to update" |
| 14 | Grace period ends — subscription suspended |
| 15 | Final in-app message: "Reactivate to keep access" |
Grace period:
Maximize grace period length — every extra day recovers more subscribers.
RevenueCat handles dunning automatically. Key settings:
See revenuecat.md integration guide.
Target lapsed subscribers (cancelled or expired in last 30–90 days).
Start with the softest offer; escalate only if no response:
Week 1 after lapse: "We miss you" — highlight new features added since they left
Week 3: "Come back for 30% off your first month back"
Week 6: "3 months at 50% off — best offer we'll make"
Week 12+: Archive — low conversion probability
| Channel | How |
|---|---|
| Push notification | In-app if app still installed |
| If email was collected | |
| Apple Win-Back Offer | Native iOS win-back offer in StoreKit 2 |
| Paid retargeting | Meta/Google retargeting to lapsed subscriber list |
Apple natively supports win-back subscription offers for lapsed subscribers:
Lifecycle Metrics ([period]):
Trial start rate: [X]% (benchmark: >20%)
Trial conversion: [X]% (benchmark: 25-40%)
M1 renewal: [X]% (benchmark: >70%)
Monthly churn: [X]% (benchmark: <5%)
Dunning recovery: [X]% (benchmark: >30%)
Win-back rate: [X]% (benchmark: 5-15%)
LTV (estimated): $[N]
MRR: $[N]
Top issues:
1. [Stage] — [metric] is [X]% vs benchmark [Y]% — [recommended fix]
2. [Stage] — [metric] is [X]% vs benchmark [Y]% — [recommended fix]
Priority action:
[Single highest-leverage change to implement this week]
monetization-strategy — Paywall design, pricing tiers, trial setupretention-optimization — Engagement strategy to reduce voluntary churnapp-analytics — Track the metrics above with Firebase + RevenueCatonboarding-optimization — Fix early-stage drop-off that prevents trial startsrating-prompt-strategy — Satisfied subscribers are your best ratersMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added subscription-lifecycle from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
subscription-lifecycle reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in subscription-lifecycle — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
subscription-lifecycle has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: subscription-lifecycle is focused, and the summary matches what you get after install.
Useful defaults in subscription-lifecycle — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for subscription-lifecycle matched our evaluation — installs cleanly and behaves as described in the markdown.
subscription-lifecycle has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added subscription-lifecycle from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
subscription-lifecycle is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 50