Guide users through transitioning from pure product-led growth to sales-assisted expansion using product usage signals.
Works with
Helps define Product Qualified Leads (PQLs) and Product Qualified Accounts (PQAs) based on actual product engagement rather than marketing metrics
Covers the complete handoff workflow: identifying usage signals that trigger sales outreach, designing smooth transitions from self-serve to sales-assisted, and aligning product and sales team incentives
Emphasizes person
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionproduct-led-salesExecute the skills CLI command in your project's root directory to begin installation:
Fetches product-led-sales 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 product-led-sales. Access via /product-led-sales 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
616
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
616
stars
Help the user implement product-led sales motions using frameworks from 2 product leaders.
When the user asks for help with product-led sales:
Elena Verna: "Product-led sales converts the usage that you've generated via self-serve into a sales opportunity and it attaches a salesperson to close a much larger contract." PLS is a distinct motion that sits between PLG and traditional sales, using product usage data to identify and prioritize sales opportunities.
Hila Qu: "How the product led funnel work for us is... our sales team get that data signal, they may send an email and reach out and say, 'Hey, I saw you were checking it out. How can I help?'" Product usage signals should trigger personalized sales outreach, not generic sequences.
Product-led sales requires new metrics like PQAs and PQLs (Product Qualified Leads) that measure product engagement rather than marketing engagement. These signals are more predictive of conversion than traditional MQLs.
The initial sales outreach in a PLS motion should offer assistance based on observed behavior, not push for an immediate sale. The user has already experienced the product - sales adds value by solving specific expansion needs.
There's a natural ceiling for self-serve revenue (typically $10K-$15K). Product-led sales helps capture the value of users who need contracts larger than what credit cards support.
For all 2 insights from 2 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
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Registry listing for product-led-sales matched our evaluation — installs cleanly and behaves as described in the markdown.
product-led-sales reduced setup friction for our internal harness; good balance of opinion and flexibility.
product-led-sales is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in product-led-sales — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
product-led-sales reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend product-led-sales for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in product-led-sales — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend product-led-sales for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for product-led-sales matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in product-led-sales — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 46