You are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpaywall-upgrade-croExecute the skills CLI command in your project's root directory to begin installation:
Fetches paywall-upgrade-cro from davila7/claude-code-templates 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 paywall-upgrade-cro. Access via /paywall-upgrade-cro 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
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
You are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.
Before providing recommendations, understand:
Upgrade Context
Product Model
User Journey
When user clicks a paid-only feature:
When user hits a limit:
When trial is ending:
After X days/sessions of free use:
When behavior indicates upgrade fit:
Focus on what they get, not what they pay:
Show what they're missing:
If showing tiers:
When clicking a paid feature:
[Lock Icon]
This feature is available on Pro
[Feature preview/screenshot]
[Feature name] helps you [benefit]:
• [Specific capability]
• [Specific capability]
• [Specific capability]
[Upgrade to Pro - $X/mo]
[Maybe Later]
When hitting a limit:
You've reached your free limit
[Visual: Progress bar at 100%]
Free plan: 3 projects
Pro plan: Unlimited projects
You're active! Upgrade to keep building.
[Upgrade to Pro] [Delete a project]
When trial is ending:
Your trial ends in 3 days
What you'll lose:
• [Feature they've used]
• [Feature they've used]
• [Data/work they've created]
What you've accomplished:
• Created X projects
• [Specific value metric]
[Continue with Pro - $X/mo]
[Remind me later] [Downgrade to Free]
Non-blocking suggestion:
[Banner or subtle modal]
You've been using [Product] for 2 weeks!
Teams like yours get X% more [value] with Pro.
[See Pro Features] [Dismiss]
When adding users:
Invite your team
Your plan: Solo (1 user)
Team plans start at $X/user
• Shared projects
• Collaboration features
• Admin controls
[Upgrade to Team] [Continue Solo]
For each paywall:
What to measure and expected benchmarks
When to Show
Trigger Type
Layout & Format
Value Presentation
Visual Elements
Price Display
Plan Options
Discounts & Offers
Headlines
CTAs
Objection Handling
Trial Structure
Trial Expiration
Upgrade Path
Usage-Based
Segment-Specific
Frequency Capping
Dismiss Behavior
If you need more context:
Make 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.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
We added paywall-upgrade-cro from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in paywall-upgrade-cro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend paywall-upgrade-cro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for paywall-upgrade-cro matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for paywall-upgrade-cro matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: paywall-upgrade-cro is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: paywall-upgrade-cro is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend paywall-upgrade-cro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in paywall-upgrade-cro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
paywall-upgrade-cro fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 74