Build meaningful mentor and sponsor relationships using frameworks from 19 product leaders.
Works with
Distinguish between mentors (advice-givers), sponsors (opportunity-creators), and coaches (accountability partners); each requires a different approach and relationship-building strategy
Start with small, specific asks that take minutes to answer via email, then build trust by following up with results before requesting larger commitments or ongoing relationships
Maintain a stable of 3–4 mento
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfinding-mentors-sponsorsExecute the skills CLI command in your project's root directory to begin installation:
Fetches finding-mentors-sponsors 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 finding-mentors-sponsors. Access via /finding-mentors-sponsors 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 meaningful mentor and sponsor relationships using approaches from 19 product leaders.
When the user asks for help finding mentors or sponsors:
Christopher Miller: "Mentors are great... but I would actually describe those folks as being sponsors and advocates, people who were willing to put up capital, whether that's professional, social capital to bet on you." Differentiate between advice-givers (mentors) and opportunity-creators (sponsors). Build trust with potential sponsors by being coachable and delivering results on their behalf.
Gibson Biddle: "Don't ask a person to be your mentor. That's really awkward. First, identify them... then find ways to be helpful. Everybody needs help." Build mentorship relationships organically by offering value first rather than making a formal request.
Jules Walter: "Make the smallest ask possible... 'Is there an example of product that you think was created with this approach?' Something he could answer in literally two minutes via email." Secure high-level mentors by starting with tiny, specific requests that require minimal effort, then build the relationship through follow-ups that show you applied their advice.
Chip Conley: "Brian would go to experts and say, 'I don't know what the hell I'm doing.'... I appreciated that a guy who had a lot of hubris could also have the humility to say, 'I want to learn more about this.'" The most effective way to learn from mentors is radical honesty about your knowledge gaps, regardless of your seniority.
Bangaly Kaba: "It's actually better to have a stable of mentors. You want to have three or four. And ideally, what you do is you meet with each one of them once a month on a different Friday." Schedule meetings with different mentors on different weeks. Ask for mentors by describing a specific challenge rather than requesting general mentorship.
Bret Taylor: "When you ask for advice, don't just ask what to do but why. Be an obnoxious two-year-old kid, why? Why? Why?" Deconstruct their advice into underlying frameworks to avoid misapplying their specific anecdotes to your different situation.
Elena Verna: "Don't think that you have unique problems. You don't... Your problem has been solved by somebody." Reach out to peers at other companies via LinkedIn or X to ask how they solved specific growth challenges. Hire advisors to provide structural frameworks for new initiatives.
Ami Vora: "I had everything I needed, people were so kind and generous, but I didn't recognize it that way because we talk about it differently." Build "emulators" of different leaders in your head to load their specific skillsets. Don't feel pressured to find one perfect mentor who matches your exact life path.
Deb Liu: "I'm in a lean-in group and we support each other... coaching circles give you an opportunity to learn from each other and to get peer coaching." Join or form a coaching circle with peers at a similar career stage to share challenges and validate whether a problem is personal or situational.
Phyl Terry: "Warren Buffett is my mentor, he just doesn't know it... if you really study that moment and study what Jobs did, it can inform your decisions." Select a leader you respect and study their specific actions during critical career moments. Read primary sources rather than just biographies.
Paul Millerd: "If we can't jump on a call, can I send you a list of questions?" When doing cold outreach, offer to send written questions instead of requesting a live call to increase response rates.
For all 23 insights from 19 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
Keeps context tight: finding-mentors-sponsors is the kind of skill you can hand to a new teammate without a long onboarding doc.
finding-mentors-sponsors fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added finding-mentors-sponsors from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: finding-mentors-sponsors is the kind of skill you can hand to a new teammate without a long onboarding doc.
finding-mentors-sponsors has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: finding-mentors-sponsors is the kind of skill you can hand to a new teammate without a long onboarding doc.
finding-mentors-sponsors has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for finding-mentors-sponsors matched our evaluation — installs cleanly and behaves as described in the markdown.
finding-mentors-sponsors reduced setup friction for our internal harness; good balance of opinion and flexibility.
finding-mentors-sponsors has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 68