FLOW SEO Framework
AgriciDaniel/claude-seo
Brings the FLOW framework's stage-specific SEO prompts into the agent, from keyword discovery through backlinks, on-page work and conversion to local SEO, loaded on demand.
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 Paywall Upgrade Cro
$ npx skills add borghei/Claude-Skills --skill paywall-upgrade-cro -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills paywall-upgrade-cro --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/business-growth/paywall-upgrade-cro .claude/skills/paywall-upgrade-cro && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "paywall-upgrade-cro" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/paywall-upgrade-cro into .claude/skills/paywall-upgrade-cro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paywall-upgrade-cro", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/business-growth/paywall-upgrade-croType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill paywall-upgrade-cro -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills paywall-upgrade-cro --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/business-growth/paywall-upgrade-cro .agents/skills/paywall-upgrade-cro && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "paywall-upgrade-cro" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/paywall-upgrade-cro into .agents/skills/paywall-upgrade-cro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paywall-upgrade-cro", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill paywall-upgrade-cro -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills paywall-upgrade-cro --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/business-growth/paywall-upgrade-cro .cursor/skills/paywall-upgrade-cro && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "paywall-upgrade-cro" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/paywall-upgrade-cro into .cursor/skills/paywall-upgrade-cro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paywall-upgrade-cro", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path business-growth/paywall-upgrade-cro--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill paywall-upgrade-cro -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills paywall-upgrade-cro --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/business-growth/paywall-upgrade-cro .gemini/skills/paywall-upgrade-cro && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "paywall-upgrade-cro" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/paywall-upgrade-cro into .gemini/skills/paywall-upgrade-cro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paywall-upgrade-cro", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills paywall-upgrade-croInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill paywall-upgrade-cro -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/business-growth/paywall-upgrade-cro .github/skills/paywall-upgrade-cro && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "paywall-upgrade-cro" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/paywall-upgrade-cro into .github/skills/paywall-upgrade-cro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paywall-upgrade-cro", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill paywall-upgrade-cro -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills paywall-upgrade-cro --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/business-growth/paywall-upgrade-cro .opencode/skills/paywall-upgrade-cro && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "paywall-upgrade-cro" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/paywall-upgrade-cro into .opencode/skills/paywall-upgrade-cro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paywall-upgrade-cro", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
paywall-upgrade-cro- GitHub stars
- 891
- Token cost
- ~5.7k tokens
- SKILL.md length
- 2,330 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 354
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 3 steps: paywall_trigger_auditor.py → upgrade_funnel_analyzer.py → paywall_copy_scorer.py
- Save offer strategy
- SKILL.md covers Table of Contents, Clarify First, Initial Assessment and The Value-First Principle, plus 7 more sections
- Runs Python scripts from its folder; calls python
What it does
Paywall Upgrade Cro is an agent skill from borghei/Claude-Skills. 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.
Its SKILL.md is about 5.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/paywall_copy_scorer.py`, `scripts/paywall_trigger_auditor.py` and `scripts/upgrade_funnel_analyzer.py`).
It sits in Marketing & SEO, covering Conversion rate optimization. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Save offer strategy
- Ethical monetization patterns
Example prompts
- “/paywall-upgrade-cro”
Requirements
- Python 3
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Paywall Upgrade Cro loads about 5.7k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 2,330 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 2,330 words, ~5,695 tokens.
Download SKILL.mdSave it as
.claude/skills/paywall-upgrade-cro/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- 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
- metadata.author
- borghei
- metadata.category
- business-growth
- metadata.updated
- 2026-03-31
- metadata.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
- Initial Assessment
- The Value-First Principle
- Paywall Trigger Architecture
- Paywall Screen Design
- Feature Gate Patterns
- Usage Limit UX
- Trial Expiration Flows
- Timing and Frequency Rules
- Upgrade Flow Optimization
- Dark Pattern Avoidance
- Platform-Specific Considerations
- Metrics and Benchmarks
- A/B Test Framework
- Output Artifacts
- Related Skills
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 | "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 | "Tomorrow is your last day" | Urgency + offer | |
| Day 14 | In-app full screen | "Your trial has ended" | Clear options |
| Day 15 | "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 Avoidance
Patterns to NEVER Use
| Dark Pattern | Why It Fails | Ethical Alternative |
|---|---|---|
| Hidden close button | Breaks trust, generates support tickets | Clear X in top-right corner |
| Shame copy ("No, I don't want to grow my business") | Manipulative, reduces brand respect | "Maybe later" or "Not now" |
| Countdown timer (fake urgency) | Users discover it resets, destroys credibility | Only use for genuinely expiring offers |
| Confusing plan selection | Users feel tricked, higher refund rate | Clear plan names with honest comparison |
| Blocking critical actions | Users feel trapped, generates churn | Allow continued use of existing features |
| Making downgrade difficult | Regulatory risk (especially in EU/CA) | One-click downgrade option |
Platform-Specific Considerations
iOS App Store
- Apple requires in-app purchase (IAP) for digital goods/services
- Apple takes 30% commission (15% for small business program)
- Must comply with App Store Review Guidelines 3.1
- Cannot link to external payment pages from within the app
- Must clearly communicate subscription terms and renewal
Google Play
- Similar IAP requirements as iOS
- Google Play billing required for digital goods
- 15% commission on first $1M in annual revenue, then 30%
- Must provide clear subscription management
Web App
- Full control over payment flow and presentation
- Can offer any payment method
- No platform commission
- Can A/B test freely without app review delays
Metrics and Benchmarks
Key Metrics
| Metric | Formula | Benchmark |
|---|---|---|
| Paywall impression rate | Users who see paywall / Active users | Track, no universal benchmark |
| Paywall CTR | Upgrade clicks / Paywall impressions | 5-15% |
| Upgrade completion rate | Completed upgrades / Upgrade clicks | 30-60% |
| Free-to-paid conversion | Paid users / Total free users | 2-5% for freemium, 15-30% for trial |
| Revenue per user (ARPU) | Total revenue / Active users | Segment-dependent |
| Post-upgrade churn (30-day) | Churned within 30 days / New paid users | < 10% |
Warning Signals
| Signal | Diagnosis | Action |
|---|---|---|
| CTR < 3% | Paywall copy or timing is wrong | Test different triggers and messaging |
| Completion < 20% | Upgrade flow has too much friction | Simplify payment flow |
| Post-upgrade churn > 15% | Value not matching expectations | Review feature access and onboarding |
| Free-to-paid < 1% | Paywall appears before value is delivered | Delay triggers until after activation |
A/B Test Framework
Show full SKILL.md (952 more words)Show less
High-Impact Tests
| Test | Hypothesis | Metric |
|---|---|---|
| Trigger timing (earlier vs later) | Later trigger = higher conversion rate | Free-to-paid conversion |
| Soft gate vs hard gate | Soft gate (preview) converts better | Feature gate CTR |
| Copy variation | Value-focused vs urgency-focused | Paywall CTR |
| Price presentation | Monthly vs annual default | ARPU |
Test Measurement
- Run for minimum 2 weeks or 100 conversions per variant
- Track upgrade rate AND 30-day post-upgrade retention
- A test that increases upgrades but increases churn is a net negative
Output Artifacts
| Artifact | Format | Description |
|---|---|---|
| Paywall Trigger Map | Trigger x timing x frequency table | All trigger points with rules and cooldowns |
| Screen Copy Set | Complete screen designs | Headline, benefits, CTA, escape hatch for each paywall type |
| Upgrade Flow Diagram | Step-by-step flow | Paywall click to post-upgrade confirmation |
| Dark Pattern Audit | Checklist | Review of existing paywall for manipulative patterns |
| Trial Expiration Sequence | Day-by-day plan | In-app + email sequence for trial countdown |
| A/B Test Backlog | Prioritized table | Test ideas ranked by expected impact |
Tool Reference
1. paywall_trigger_auditor.py
Audits paywall trigger configuration for timing, frequency, and coverage issues. Reads a JSON file of trigger rules and user event data, then flags misconfigured triggers, missing cooldowns, and dark-pattern risks.
python scripts/paywall_trigger_auditor.py triggers.json --format text
python scripts/paywall_trigger_auditor.py triggers.json --format json| Flag | Type | Description |
|---|---|---|
triggers.json | positional | Path to JSON file with trigger rules and event data |
--format | optional | Output format: text (default) or json |
2. upgrade_funnel_analyzer.py
Analyzes upgrade funnel step-by-step conversion from paywall impression through payment completion. Identifies the highest-drop steps, calculates stage-over-stage conversion, and benchmarks against industry targets.
python scripts/upgrade_funnel_analyzer.py funnel.json --format text
python scripts/upgrade_funnel_analyzer.py funnel.json --format json| Flag | Type | Description |
|---|---|---|
funnel.json | positional | Path to JSON file with funnel step data |
--format | optional | Output format: text (default) or json |
3. paywall_copy_scorer.py
Scores paywall screen copy against proven conversion patterns. Evaluates headline structure, benefit clarity, CTA strength, social proof presence, and dark-pattern risk. Outputs a 0-100 score with itemized feedback.
python scripts/paywall_copy_scorer.py copy.json --format text
python scripts/paywall_copy_scorer.py copy.json --format json| Flag | Type | Description |
|---|---|---|
copy.json | positional | Path to JSON file with paywall copy elements |
--format | optional | Output format: text (default) or json |
Troubleshooting
| Problem | Likely Cause | Resolution |
|---|---|---|
| Paywall CTR below 3% | Trigger fires before user reaches aha moment or copy is feature-focused instead of benefit-focused | Delay trigger until after activation event; rewrite headline to outcome-based messaging (lifts CTR up to 23% per Strava case study) |
| Upgrade completion below 20% | Too much friction in payment flow (redirects, missing payment methods, surprise charges) | Keep flow in-context (modal/slide-out), pre-fill known info, show price before payment step |
| Post-upgrade churn above 15% | Value expectation mismatch -- paid experience does not match what the paywall promised | Audit feature access post-upgrade, add guided tour of newly unlocked features, align copy with actual capabilities |
| Free-to-paid conversion below 1% | Paywall appears before value is delivered or free tier is too generous | Map activation events and ensure paywall only fires after aha moment; review free vs paid feature boundary |
| Users close paywall within 1 second repeatedly | Paywall is interrupting workflow or appearing too frequently | Increase cooldown to 7+ days after dismissal, cap at 3 per month, switch to less intrusive format (banner vs modal) |
| Mobile paywall underperforms desktop by >30% | iOS/Android IAP friction, small dismiss targets, or full-screen overlay on mobile | Ensure 44x44px touch targets, use bottom-sheet format on mobile, comply with App Store guidelines |
| Trial expiration emails have low open rate | Generic subject lines, wrong send timing, or email deliverability issues | Personalize with usage data ("You created 12 projects"), send at user's active hours, check spam score |
Success Criteria
- Free-to-paid conversion rate reaches 2-5% for freemium models or 15-30% for trial models within 90 days of optimization
- Paywall CTR stabilizes at 5-15% across all trigger types
- Upgrade completion rate (paywall click to payment) exceeds 30%
- Post-upgrade 30-day retention exceeds 90% (churn below 10%)
- Paywall annoyance signals (sub-1-second dismissals) decrease to below 5% of impressions
- Zero dark patterns present in paywall audit (no shame copy, no hidden close buttons, no fake urgency)
- Annual plan adoption reaches 40%+ of new upgrades when annual toggle defaults are implemented (benchmark: 20-40% lift)
Scope & Limitations
In scope: In-product upgrade flows including feature gates, usage limit screens, trial expiration sequences, upgrade trigger timing, save offer strategy, paywall screen design, and A/B test frameworks for freemium-to-paid and trial-to-paid conversion.
Out of scope: Public-facing pricing pages (use page-cro), the pricing model itself (use pricing-strategy), post-signup onboarding before the aha moment (use onboarding-cro), initial registration flows (use signup-flow-cro), and post-upgrade churn intervention (use churn-prevention). This skill does not cover App Store Optimization (ASO) or paid acquisition strategies. Scripts operate on local data only -- no integrations with payment processors, analytics platforms, or A/B testing tools.
Limitations: Conversion benchmarks are based on aggregate SaaS/app industry data and may vary significantly by vertical, price point, and audience. Mobile paywall performance is highly dependent on platform-specific IAP requirements (Apple 30% commission, Google Play billing). Scripts analyze static snapshots; real-time paywall optimization requires integration with analytics and experimentation platforms not provided here.
Integration Points
- pricing-strategy -- Feed pricing tier structure and value metric into paywall copy and plan comparison design
- onboarding-cro -- Coordinate activation event definitions; paywall triggers should fire only after onboarding confirms aha moment
- churn-prevention -- Post-upgrade churn data feeds back into paywall expectation-setting; save offers should align with churn prevention playbook
- page-cro -- Public pricing page design feeds into in-app upgrade flow consistency; ensure messaging alignment
- signup-flow-cro -- Registration flow completion triggers trial start; trial duration and paywall timing depend on signup context
- popup-cro -- Share frequency capping logic and suppression rules; paywall modals follow same UX principles as marketing popups
Related Skills
- page-cro -- Use for public pricing page optimization. Paywall-upgrade-cro handles in-product upgrade moments.
- onboarding-cro -- Use when users have not reached activation. Do not show paywalls before the aha moment.
- pricing-strategy -- Use when the pricing model itself needs redesigning (tier structure, value metric, price points).
- churn-prevention -- Use when users upgrade but then churn. If they never upgrade, the problem is here.
- signup-flow-cro -- Use for the initial registration flow. Paywall-upgrade-cro handles post-signup monetization.
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts) in business-growth/paywall-upgrade-cro of borghei/Claude-Skills.
- SKILL.md
- scripts/paywall_copy_scorer.py
- scripts/paywall_trigger_auditor.py
- scripts/upgrade_funnel_analyzer.py
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Paywall Upgrade Cro next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Paywall Upgrade Cro this skillborghei/Claude-Skills | 891 | — | ~5.7k | Automated safety check: Pass | MIT | |
| FLOW SEO FrameworkAgriciDaniel/claude-seo | 19k | 2 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Paywallscoreyhaines31/marketingskills | 54k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Onboarding Crofreekmurze/dotfiles | 1k | 16 repos | ~1.6k | Automated safety check: Pass | None | |
| Paywall Upgrade Crofreekmurze/dotfiles | 1k | 15 repos | ~1.4k | Automated safety check: Pass | None | |
| Revenue Centric Designheliocosta-dev/revenue-centric-design | 740 | — | ~1.6k | Automated safety check: Pass | Custom licence |
Similar skills
Paywalls
coreyhaines31/marketingskills
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.
Onboarding Cro
freekmurze/dotfiles
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.
Paywall Upgrade Cro
freekmurze/dotfiles
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.
Revenue Centric Design
heliocosta-dev/revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…
Google Analytics
thatrebeccarae/claude-marketing
Analyze Google Analytics data, review website performance metrics, identify traffic patterns, and suggest data-driven improvements.
More from borghei/Claude-Skills
All 354 skills in this repoAgent Harness
borghei/Claude-Skills
Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.
Agents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Related
Categories
Questions about Paywall Upgrade Cro
What does Paywall Upgrade Cro do?
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. Paywall Upgrade Cro is an agent skill from borghei/Claude-Skills. 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.
When should I use Paywall Upgrade Cro?
Paywall Upgrade Cro fits situations like: save offer strategy; ethical monetization patterns.
How do I install Paywall Upgrade Cro in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill paywall-upgrade-cro -a claude-code`. Or copy the skill folder (business-growth/paywall-upgrade-cro in borghei/Claude-Skills) into .claude/skills/paywall-upgrade-cro in your project. Claude Code loads it when a task matches its description.
How do I install Paywall Upgrade Cro in Codex?
Run `npx skills add borghei/Claude-Skills --skill paywall-upgrade-cro -a codex`. Or copy the skill folder (business-growth/paywall-upgrade-cro in borghei/Claude-Skills) into .agents/skills/paywall-upgrade-cro in your project. Codex loads it when a task matches its description.
Can I use Paywall Upgrade Cro in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill paywall-upgrade-cro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paywall-upgrade-cro, .gemini/skills/paywall-upgrade-cro, .github/skills/paywall-upgrade-cro and .opencode/skills/paywall-upgrade-cro in your project.
What does Paywall Upgrade Cro need to run?
Going by SKILL.md and its folder, Paywall Upgrade Cro needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Paywall Upgrade Cro access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Paywall Upgrade Cro safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Paywall Upgrade Cro use?
Paywall Upgrade Cro is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Paywall Upgrade Cro use?
About 5.7k tokens (SKILL.md is roughly 23k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Paywall Upgrade Cro?
Skills that share tags, products or a category with Paywall Upgrade Cro: FLOW SEO Framework (AgriciDaniel/claude-seo, 19k stars), Paywalls (coreyhaines31/marketingskills, 54k stars), Onboarding Cro (freekmurze/dotfiles, 1k stars) and Paywall Upgrade Cro (freekmurze/dotfiles, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Paywall Upgrade Cro?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 891 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.