paywall-upgrade-cro
by alirezarezvanipaywall-upgrade-cro is a marketing skill for improving in-app paywalls, upgrade screens, upsell modals, feature gates, limit-reached prompts, and freemium conversion flows after users have experienced product value.
This skill scores 74/100, which means it is acceptable for directory listing and should help agents handle in-product paywall and upgrade-screen CRO with less guesswork than a generic prompt. Directory users should see it as a focused marketing workflow skill with good triggering and conceptual structure, but limited supporting artifacts for validation, examples, or installation guidance.
- Strong triggerability: the frontmatter explicitly covers paywalls, upgrade screens, upsell modals, feature gates, trial expiration, limit-reached screens, and in-app pricing, while distinguishing it from public pricing-page CRO.
- Clear initial operating frame: it tells the agent to check `.claude/product-marketing-context.md` first and assess upgrade context, product model, and user journey before recommending changes.
- Substantive workflow content: the SKILL.md is sizeable, with many headings and no placeholder markers or experimental signals, suggesting real guidance rather than a demo stub.
- No support files, references, scripts, or README are present, so users only have SKILL.md to judge and operate the workflow.
- Structural signals show low practical artifact coverage, which may mean fewer concrete examples, templates, or implementation aids than a stronger CRO skill would provide.
Overview of paywall-upgrade-cro skill
What paywall-upgrade-cro is for
paywall-upgrade-cro is a marketing skill for improving in-product conversion moments: paywalls, upgrade screens, upsell modals, feature gates, limit-reached screens, trial-expiration prompts, and plan upgrade flows. It is built for situations where a user has already experienced some value and now needs a clear reason to pay, upgrade, or unlock more.
Best-fit users and projects
This skill is a good fit for SaaS, mobile apps, freemium tools, productivity products, AI apps, marketplaces, and subscription products that convert users inside the product rather than only on a public pricing page. Product marketers, founders, growth teams, designers, and PMs can use it to turn a vague upgrade idea into stronger paywall copy, layout guidance, objection handling, and test hypotheses.
What makes the skill different
The key distinction is context: paywall-upgrade-cro focuses on upgrade moments after product value has been demonstrated. It is not a generic pricing-page prompt. The source skill emphasizes assessing the upgrade context, product model, trigger moment, user journey, value proof, and friction before recommending changes. That makes it more useful for feature gates and in-app prompts than broad conversion advice.
When not to use it
Do not use this skill as your main framework for homepage CRO, public pricing pages, SEO landing pages, lifecycle emails, or ad creative. It can inform the offer and messaging, but its strongest use case is the in-product decision point where the user is interrupted, blocked, nudged, or invited to upgrade.
How to Use paywall-upgrade-cro skill
paywall-upgrade-cro install and repository path
Install the skill from the repository path:
npx skills add alirezarezvani/claude-skills --skill paywall-upgrade-cro
The upstream file to inspect first is:
marketing-skill/skills/paywall-upgrade-cro/SKILL.md
There are no extra scripts, rule folders, or reference assets in the current file tree, so the main value is in the structured decision framework inside SKILL.md. If your environment supports skill invocation automatically, use phrases such as “improve this paywall,” “optimize this upgrade modal,” “rewrite this feature gate,” or “increase freemium-to-paid conversion.”
Inputs the skill needs
For useful output, provide more than the screen copy. Include the upgrade context, user state, trigger, and business model. Strong inputs usually include:
- Product type and target user
- Free plan value already experienced
- Paid feature or plan being promoted
- Moment when the paywall appears
- Current screen copy or wireframe
- Pricing and trial terms
- Known objections, support complaints, or analytics
- Conversion goal, such as trial start, paid subscription, add-on purchase, or tier upgrade
Weak prompt: “Improve our upgrade screen.”
Stronger prompt: “Use paywall-upgrade-cro for Conversion. We have a freemium AI note app. Users hit this modal after creating 5 summaries. The paid plan unlocks unlimited summaries, export, and team sharing at $12/month. Current conversion from the limit screen is 2.1%. Rewrite the modal, explain the value hierarchy, suggest layout changes, and propose 3 A/B tests.”
Suggested workflow for better usage
Start by asking the model to diagnose the paywall before rewriting it. A practical paywall-upgrade-cro usage workflow is:
- Summarize the upgrade moment and user motivation.
- Identify whether the user has experienced enough value before the ask.
- Map the paid feature to the user’s current blocked goal.
- Rewrite headline, subhead, benefits, CTA, reassurance, and objection handling.
- Suggest what to remove if the screen is overloaded.
- Propose A/B tests tied to one clear hypothesis each.
This sequence prevents the output from becoming generic “unlock premium” copy.
Repository-reading path
Read SKILL.md from top to bottom once before relying on the skill in production. Pay special attention to the initial assessment section and core principles such as “value before ask” and “show, don’t just tell.” These sections reveal how the skill decides whether a paywall should emphasize urgency, feature access, outcome proof, usage limits, trial continuation, or tier comparison.
paywall-upgrade-cro skill FAQ
Is paywall-upgrade-cro beginner friendly?
Yes, but it works best when you can describe the product journey. A beginner can use it to generate a first upgrade screen, but the quality improves sharply when you provide the exact trigger moment, what the user just accomplished, and why the paid plan is the logical next step.
How is it different from an ordinary CRO prompt?
A generic CRO prompt may suggest clearer CTAs, shorter copy, social proof, or urgency. The paywall-upgrade-cro skill is narrower: it starts from the in-app context and asks whether the paywall appears at the right time, whether the user has seen enough value, and whether the upgrade message connects to the action they are trying to complete.
Can it design pricing strategy?
It can help frame plans, compare tiers, and surface offer friction, but it is not a full pricing research system. Use it for paywall presentation and upgrade-flow conversion. For pricing architecture, willingness-to-pay research, or packaging strategy, pair it with customer data, pricing analysis, and product strategy work.
What blocks good results?
The biggest blockers are missing context and premature paywalls. If you only provide copy, the model may polish the words without fixing the conversion problem. If the user has not experienced value before the ask, the right recommendation may be to delay, change, or soften the prompt rather than make it more aggressive.
How to Improve paywall-upgrade-cro skill
Improve paywall-upgrade-cro with stronger context
To get better results from paywall-upgrade-cro, give the model the “before” and “after” state. Explain what the user was doing, what they achieved, what is now blocked, and what paid access changes. This helps the skill write copy around momentum instead of abstract premium benefits.
Useful format:
- “User just did…”
- “Now they want to…”
- “We block or interrupt because…”
- “Paid plan unlocks…”
- “Main hesitation is likely…”
- “Success metric is…”
Common failure modes to watch
Watch for outputs that overuse urgency, exaggerate value, or ignore the user’s current task. In-app upgrade prompts often fail when they feel like a sales interruption instead of a helpful continuation. Also check whether the CTA matches the commitment level: “Start free trial,” “Upgrade now,” “Unlock exports,” and “Compare plans” create different expectations.
How to iterate after the first output
Do not stop at one rewrite. Ask for variants based on different hypotheses:
- Value-led: emphasize the outcome the user already wants.
- Limit-led: explain the usage cap clearly and fairly.
- Proof-led: show saved time, completed work, or team benefit.
- Low-friction: reduce anxiety with trial, cancellation, or billing reassurance.
Then ask the model to rank variants by likely fit for your product stage and user intent.
What to measure after implementation
Pair the paywall-upgrade-cro guide output with analytics. Track view-to-click rate, click-to-checkout rate, trial-start rate, paid conversion, dismissals, support complaints, and downstream retention. A paywall that increases short-term upgrades but worsens refunds or churn is not a conversion win.