SkillAgentSearch skills...

paywall-upgrade-cro

In-app paywall and upgrade screen optimization covering feature gate design, usage limit UX, trial expiration flows, upgrade trigger timing, save offer strategy, and ethical monetization patterns.

Install / Use

npx skills add borghei/Claude-Skills --skill paywall-upgrade-cro

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

92/100

Supported Platforms

Universal

Our assessment of paywall-upgrade-cro

paywall-upgrade-cro scores 92/100 on our quality scale, 942nd of 4,702 Development & Engineering skills we index (top 21%).

Its SKILL.md is 22 KB long, well organised into 53 sections with 9 code examples: a thorough specification that gives an agent plenty to work with.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so paywall-upgrade-cro is actively maintained.
  • Our last check on 2026-10-28 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

paywall-upgrade-cro compared with similar skills

All 4 of these similar skills score higher than paywall-upgrade-cro; compare them before choosing.

SkillScoreStarsUpdatedFormat
paywall-upgrade-cro (this skill)by borghei9281757d agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.9k8d agoCLAUDE.md

Frequently asked questions

How do I install paywall-upgrade-cro?
Run npx skills add borghei/Claude-Skills --skill paywall-upgrade-cro. The install tabs above show the steps for each supported agent.
Which AI agents does paywall-upgrade-cro work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is paywall-upgrade-cro safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is paywall-upgrade-cro still maintained?
The repository was last updated about 2 months ago, so paywall-upgrade-cro is actively maintained.

name: paywall-upgrade-cro description: > In-app paywall and upgrade screen optimization covering feature gate design, usage limit UX, trial expiration flows, upgrade trigger timing, save offer strategy, and ethical monetization patterns. license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: business-growth updated: 2026-03-31 tags: [cro, paywall, upgrade, freemium, monetization, upsell]

Paywall & Upgrade Screen CRO

Production-grade framework for in-product upgrade flows. Covers feature gate design, usage limit UX, trial expiration sequences, upgrade trigger timing, dark pattern avoidance, and ethical monetization. Distinct from public pricing pages (use page-cro for those) -- this focuses on in-product moments where users have already experienced value.


Table of Contents


Clarify First

Before designing the paywall, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • [ ] Upgrade model — freemium-to-paid, trial-to-paid, or tier upgrade (determines the paywall type and trigger architecture)
  • [ ] Free vs paid boundary — what is gated (defines the value gap the paywall communicates)
  • [ ] Aha moment — so triggers fire only after value is experienced (the value-first principle)
  • [ ] Platform — web, iOS, or Android (IAP rules and commissions constrain web vs app flows)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the deliverable.

Initial Assessment

Required Context

| Question | Why It Matters | |----------|---------------| | What is the upgrade model? (freemium to paid, trial to paid, tier upgrade) | Determines the paywall type | | What is free vs paid? | Defines the value gap to communicate | | What triggers upgrade prompts today? | Identifies current trigger points | | What is the current free-to-paid conversion rate? | Baseline for improvement | | What is the aha moment for users? | Determines when the paywall should appear | | What pricing model? (per seat, usage, flat) | Affects paywall messaging | | Mobile app, web app, or both? | Platform-specific requirements |


The Value-First Principle

The single most important rule in paywall design: The user must have experienced real value before seeing an upgrade prompt.

Value-First Checklist

  • [ ] User has completed the activation event (aha moment reached)
  • [ ] User has used the product at least 2-3 times
  • [ ] User has created or stored data they would lose
  • [ ] The upgrade feels like a natural next step, not a trap

When to Show vs When NOT to Show

| Show | Do Not Show | |------|------------| | After aha moment is reached | During onboarding | | When user hits a genuine limit | On first login | | When user clicks a paid feature | When user is in the middle of a task | | After milestone completion | Immediately after a frustrating experience | | On session start (gentle reminder) | After every action |


Paywall Trigger Architecture

Trigger Types

| Trigger | When It Fires | Best For | |---------|--------------|----------| | Feature gate | User clicks a locked feature | Feature-differentiated tiers | | Usage limit | User reaches a quota | Usage-based pricing | | Trial expiration | Trial period ending | Time-limited trial models | | Time-based | After N days of active use | Freemium nurture | | Milestone-based | After user achieves X | Upsell at success moments | | Team-based | When team grows past free seat limit | Per-seat models |

Trigger Priority Map

| User State | Primary Trigger | Timing | |-----------|----------------|--------| | Activated, under limits | Feature gate (when they try paid feature) | On click | | Approaching limit | Soft warning (80% of limit) | Proactive | | Hit limit | Usage limit paywall | On action that exceeds limit | | Trial day 7 of 14 | Trial ending reminder | Session start | | Trial day 13 of 14 | Urgent trial expiration | Session start + email | | Trial day 14 | Trial expired | On login | | Active for 30+ days, free | Value-based upgrade prompt | Session start, once per week |


Paywall Screen Design

Screen Anatomy

┌─────────────────────────────────────┐
│ [X Close / "Not now"]               │  Escape hatch (always visible)
│                                     │
│ HEADLINE: Value-focused             │  "Unlock [feature] to [benefit]"
│                                     │
│ [Feature preview / screenshot]      │  Show what they are missing
│                                     │
│ KEY BENEFITS:                       │
│ - Benefit 1                        │
│ - Benefit 2                        │
│ - Benefit 3                        │
│                                     │
│ PRICE: $X/month                    │  Clear, simple pricing
│ (or plan comparison)               │
│                                     │
│ [UPGRADE CTA - Primary]           │  "Start Pro Plan"
│ [Maybe Later - Secondary]          │  Clear secondary action
│                                     │
│ "Join 5,000+ teams on Pro"        │  Social proof
└─────────────────────────────────────┘

Copy Patterns by Trigger Type

| Trigger | Headline Pattern | CTA Pattern | |---------|-----------------|-------------| | Feature gate | "Unlock [Feature] to [Benefit]" | "Upgrade to [Plan]" | | Usage limit | "You've used all [N] [resources]" | "Get Unlimited [Resources]" | | Trial expiring | "Your trial ends in [N] days" | "Continue with [Plan]" | | Milestone | "You just hit [milestone]! Keep growing with Pro" | "Upgrade & Keep Growing" | | Time-based | "[Product] Pro helps teams like yours [benefit]" | "See Pro Features" |


Feature Gate Patterns

Soft Gate (Preview + Lock)

User can see what the feature does but cannot use it fully.

┌──────────────────────────────┐
│  [Feature Preview]           │  Blurred screenshot or partial result
│                              │
│  [Lock Icon] Pro Feature     │
│                              │
│  [Feature name] lets you:    │
│  - Capability 1              │
│  - Capability 2              │
│                              │
│  [Upgrade to Pro - $X/mo]   │
│  [Maybe Later]              │
└──────────────────────────────┘

Hard Gate (Block + Explain)

User cannot access the feature at all. Show the value clearly.

┌──────────────────────────────┐
│  [Lock Icon]                 │
│                              │
│  This feature is available   │
│  on the Pro plan             │
│                              │
│  What you get:               │
│  - Benefit 1                 │
│  - Benefit 2                 │
│  - Benefit 3                 │
│                              │
│  [Upgrade to Pro]            │
│  [Compare Plans]             │
└──────────────────────────────┘

Feature Gate Design Rules

  • Always explain WHY the feature is valuable (not just that it is locked)
  • Show what the feature produces (output preview) when possible
  • Include a "Compare Plans" link for users who want more detail
  • Do not gate features the user was already using during trial

Usage Limit UX

Approaching Limit (80% Warning)

┌──────────────────────────────────┐
│  [Progress Bar: 80%]            │
│  You've used 80 of 100 credits  │
│                                  │
│  [Get More Credits]  [Dismiss]  │
└──────────────────────────────────┘

At Limit (100%)

┌──────────────────────────────────────┐
│  [Progress Bar: 100%]               │
│  You've reached your monthly limit  │
│                                      │
│  Free: 100 credits | Pro: Unlimited │
│                                      │
│  [Upgrade to Pro]                   │
│  [Delete items to free space]       │  Alternative action
└──────────────────────────────────────┘

Usage Limit Rules

  • Show usage context before the limit hits (progress indicators in the UI)
  • Provide an alternative action (delete, archive, export) when possible
  • Never delete user data when limits are reached
  • Allow grace period (do not cut off mid-task)

Trial Expiration Flows

Trial Countdown Sequence

| Day | Channel | Message | Tone | |-----|---------|---------|------| | Day 7 (of 14) | In-app banner | "7 days left in your trial" | Informational | | Day 10 | Email | "4 days left -- here's what you've accomplished" | Value summary | | Day 12 | In-app modal | "2 days left -- don't lose access to [feature]" | Mild urgency | | Day 13 | Email | "Tomorrow is your last day" | Urgency + offer | | Day 14 | In-app full screen | "Your trial has ended" | Clear options | | Day 15 | Email | "We kept your data safe -- reactivate anytime" | Reassurance |

Trial Expiration Screen Design

┌─────────────────────────────────────────┐
│  Your trial has ended                    │
│                                          │
│  What you accomplished during trial:     │
│  - Created [N] projects                 │  Personalized data
│  - Invited [N] team members             │
│  - Saved an estimated [X] hours         │
│                                          │
│  What happens now:                       │
│  - Your data is saved for 30 days       │
│  - Read-only access to existing work    │
│  - Full access resumes when you upgrade │
│                                          │
│  [Continue with Pro - $X/mo]            │
│  [Remind Me Later]  [Downgrade to Free] │
└─────────────────────────────────────────┘

Timing and Frequency Rules

Frequency Caps

| Rule | Implementation | |------|---------------| | Max 1 paywall per session | Do not interrupt twice in one visit | | 3-7 day cooldown after dismissal | If they click "Not now", wait at least 3 days | | Never during active task | If user is creating, editing, or mid-workflow, do not interrupt | | Cap at 3 per month | After 3 dismissals in a month, stop showing until next month | | Track annoyance signals | If user closes paywall within 1 second repeatedly, increase cooldown |

Escalation Pattern

| Attempt | Approach | Invasiveness | |---------|----------|-------------| | 1 | Subtle banner or sidebar widget | Low | | 2 | Modal with value proposition | Medium | | 3 | Modal with special offer (discount/extended trial) | Medium-High | | 4+ | Reduce frequency, switch to email nurture | Low (change channel) |


Upgrade Flow Optimization

From Paywall Click to Payment

| Step | Optimization | |------|-------------| | 1. Click upgrade CTA | Opens upgrade flow (do not redirect to external page if avoidable) | | 2. Plan selection | Pre-select the recommended plan, show comparison | | 3. Payment | Pre-fill known info (email, name), support all payment methods | | 4. Confirmation | Immediate access to paid features, confirmation email | | 5. Post-upgrade | Guide to newly unlocked features, celebration moment |

Friction Reduction

  • Keep the upgrade flow in-context (modal or slide-out, not a full page redirect)
  • Pre-fill all known information
  • Support saved payment methods and one-click upgrade for returning upgraders
  • Show price clearly before the payment step (no surprise charges)

Dark Pattern Av

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars817
CategoryDevelopment
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium