Navigate enterprise sales deals through buying committee dynamics, procurement, and overcoming customer indecision.
Works with
Helps identify deal stage, map stakeholders (champion, economic buyer, decision-makers), and arm internal advocates with role-specific materials
Addresses the root cause of deal loss: customer fear of messing up and being blamed, not just competitive pressure or missing urgency
Guides procurement navigation by proactively handling administrative burden, compliance requi
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionenterprise-salesExecute the skills CLI command in your project's root directory to begin installation:
Fetches enterprise-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 enterprise-sales. Access via /enterprise-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 navigate enterprise sales using frameworks from 9 product leaders who have closed large enterprise deals at companies from Stripe to Superhuman.
When the user asks for help with enterprise sales:
Matt Dixon: "Our analysis showed that anywhere between 40 and 60% of the average salesperson's qualified pipelines will be ultimately marked as closed loss, no decision." Most deals are lost not to competitors, but to customer inertia and fear.
April Dunford: "Typically we have between five and seven people involved in what we call making the decision. By far the most important persona is what we call the champion - this person's job is to get consensus and champion the deal across everybody." Arm them with materials for IT, Legal, and the Economic Buyer.
Matt Dixon: "The omission bias is the fact that people don't want to be blamed for making decisions that lead to a loss. People are okay with missing out. They are not okay with messing up and being blamed." Address Fear of Messing Up, not just Fear of Missing Out.
Jen Abel: "When you get to procurement, you're going to have to do all the work. Make their job easy. Give me the forms that you need to fill out. I'll fill them out for you." Proactively handle the administrative burden to avoid being sidelined.
Madhavan Ramanujam: "The POC should be framed as the entire goal of the POC is to create a business case, period, full stop. It is not to demonstrate product functionality." Treat POCs as collaborative exercises to build ROI models.
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." Identify the escalator from individual use case to enterprise-level solution.
Matt Dixon: "What great salespeople do is they know that while they'll stand by those claims, they try to under-promise and over-deliver. Build your business case around a 5X improvement, then let's set up to over-deliver against that." Build cases around conservative, 100% achievable numbers.
Matt Dixon outlines four steps to overcome indecision: Judge the level of indecision, Offer a firm recommendation, Limit exploration by building trust, Take risk off the table by de-risking the deal.
For all 25 insights from 9 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
ailabs-393/ai-labs-claude-skills
Keeps context tight: enterprise-sales is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in enterprise-sales — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
enterprise-sales has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for enterprise-sales matched our evaluation — installs cleanly and behaves as described in the markdown.
enterprise-sales fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
enterprise-sales reduced setup friction for our internal harness; good balance of opinion and flexibility.
enterprise-sales is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added enterprise-sales from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: enterprise-sales is focused, and the summary matches what you get after install.
enterprise-sales fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 46