Framework-driven pricing design and optimization using insights from 46 product leaders.
Works with
Guides users through understanding business models, assessing value delivery, identifying constraints, and designing iterative pricing strategies
Emphasizes willingness-to-pay research as the foundation for pricing decisions and product roadmap prioritization
Covers key transitions: freemium vs. paid models, self-serve to sales-led (around $10K–$15K ARR), and sampling premium features in free tie
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpricing-strategyExecute the skills CLI command in your project's root directory to begin installation:
Fetches pricing-strategy from refoundai/lenny-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 pricing-strategy. Access via /pricing-strategy 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
612
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
612
stars
Help the user design and optimize pricing strategies using frameworks from 46 product leaders.
When the user asks for help with pricing:
Madhavan Ramanujam: "When we think about price, we think about it as a measure. Like liter is a measure of volume, price is a measure of value. And when you think of it this way, it really stands for, do people actually want your product?" Use willingness to pay (WTP) as a proxy for product value and conduct WTP conversations early in the development cycle.
Naomi Ionita: "Do not set it and forget it. I see companies do this, where they labor over designs and features... And then pricing's sort of plucked out of thin air, and then they don't revisit it." Treat pricing as a living part of the product roadmap, revisiting it every 6-12 months as new value is added.
Elena Verna: "Self-serve monetization has a cap of about $10,000. That's just how much we're able to process on the credit cards before they start getting flagged and declined." Transition to sales-led motions for contracts exceeding $10,000-$15,000 due to technical payment limits and individual spending authority.
Albert Cheng: "What if we actually sampled a number of different paid suggestions and interspersed them to free users across their writing? All of a sudden, people were seeing Grammarly as a much more powerful tool." Interspersing paid features within the free experience is more effective for conversion than keeping them hidden behind a hard paywall.
Archie Abrams: "When you can lower the barriers to monetary friction in some form... you can actually causally change your ability to become successful, because I've given you a little bit more time to try that idea." Reducing early monetary friction can causally improve user success by extending their "runway" to find value in the product.
Madhavan Ramanujam: "You cannot prioritize a product roadmap without having a willingness to pay conversation. If you're just prioritizing based on what you think or what you feel or technical resources, you're getting it wrong." Prioritize the 20% of features that drive 80% of the willingness to pay.
Eeke de Milliano: "Move faster on reversible decisions like pricing by grandfathering existing users." Most pricing changes can be reversed or adjusted, especially when you protect existing customers through grandfathering.
For all 76 insights from 46 guests, see references/guest-insights.md
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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added pricing-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: pricing-strategy is focused, and the summary matches what you get after install.
pricing-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: pricing-strategy is focused, and the summary matches what you get after install.
We added pricing-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: pricing-strategy is focused, and the summary matches what you get after install.
Keeps context tight: pricing-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added pricing-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
pricing-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
pricing-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 49