Strategic partnership and BD guidance grounded in insights from nine product leaders.
Works with
Covers four core phases: understanding opportunities, assessing network vs. merit dynamics, designing pitches that show mutual benefit, and navigating negotiations with timing and leverage
Emphasizes industry-specific dynamics—relationships dominate in healthcare, finance, and enterprise, while product merit matters more elsewhere
Advises building scalable partner platforms rather than one-off deals
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpartnership-bdExecute the skills CLI command in your project's root directory to begin installation:
Fetches partnership-bd 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 partnership-bd. Access via /partnership-bd 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 build strategic partnerships and business development deals using insights from 9 product leaders.
When the user asks for help with partnerships or BD:
Ayo Omojola: "Very often the way to make things happen is network-dependent, not necessarily about the merit of the thing itself. There are companies that exist because the founders know the CEO of every major payer." In industries like healthcare, finance, or enterprise, relationships matter more than product. Determine if your business is network-dependent early.
Adam Grenier: "Let me into your alpha, because I have five years of experience buying mobile ads. If you get us to work, we're a killer case study for a category you want to grow." When partnering with major platforms, show how your success helps them prove their business model. Offer to be an alpha tester for new features.
Keith Yandell: "We'll build you a product so you won't need to ask us every time. Then you'll know the parameters in which you can negotiate." Effective BD teams work with Product to create self-serve platforms for partners rather than negotiating one-off integrations. This increases velocity and reduces engineering load.
Jason Droege: "McDonald's approached us and I said 'No.' I pushed them off for four or five months. It ended up being a net benefit because we got a great deal." Don't rush into partnerships just because of the partner's size. Initial resistance can lead to better terms or exclusivity.
Jen Abel: "The problem with channel partnerships is there are a hundred of you on the list and you're expecting them to sell on your behalf. They're not visionaries, they're consultants." Don't expect Accenture or Deloitte to evangelize your product. They lack the founder's vision-casting ability.
Julia Schottenstein: "Use that corp dev team to your advantage. Take that meeting, say you're not interested in acquisition yet, but push them for an introduction to someone who could sponsor the deal - usually someone in Product or a GM." Corp dev teams are gateways to internal sponsors even if you're not looking to sell.
Meltem Kuran: "VCs ask portfolio companies 'What platform do you trust for hiring?' So people go to their VCs for that kind of question." The best partners are those your target audience already consults at the exact moment the problem arises.
Tobi Lutke: "Being a good partner is like a corporate marshmallow test companies tend to fail. The correct way to play iterated prisoner's dilemma is coordinate for both sides - it's way more valuable over long periods." Resist pulling future profits forward at the expense of a partner. Long-term coordination always beats short-term defection.
Keith Yandell: "We should have tested this at one hotel with hacky operations before asking for product resources." Validate partnership hypotheses with manual operations before committing engineering time. Dream big, start small.
For all 11 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
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
partnership-bd reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend partnership-bd for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
partnership-bd reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: partnership-bd is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend partnership-bd for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
partnership-bd has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend partnership-bd for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
partnership-bd fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
partnership-bd reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for partnership-bd matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 69