refoundai/lenny-skills
86 skills156k installs102k starsGitHub
Install
npx skills add https://github.com/refoundai/lenny-skillsSkills in this repo
1Personal ProductivityHelp users manage their time and tasks more effectively. Use when someone is overwhelmed with work, struggling with focus, trying to balance multiple responsibilities, or asking how to get more done. --- name: personal-productivity description: Help users manage their time and tasks more effectively. Use when someone is overwhelmed with work, struggling with focus, trying to balance multiple responsibilities, or asking how to get more done. --- # Personal Productivity Help the user manage their time and tasks more effectively using techniques from 2 product leaders. ## How to Help When the user asks for help with personal productivity: 1. **Understand their situation** - Ask what's overwhelming them, how they currently manage their time, and what outcomes they're trying to achieve 2. **Identify the bottleneck** - Determine if the issue is prioritization, focus, energy management, or too many commitments 3. **Apply practical techniques** - Help them implement time-boxing, task capture systems, or scheduling strategies 4.5.6kinstalls2Competitive AnalysisCompetitive Analysis helps users understand and respond to competition using frameworks from forty-nine product leaders cited in Lenny's Podcast skill library. It expands the competitive set beyond direct rivals to spreadsheets, pen-and-paper workarounds, and no-decision losses that April Dunford notes can account for roughly forty percent of B2B deals. Core principles include defining competitive alternatives first, understanding industry economics per Hamilton Helmer, grounding analysis in customer and market perspective per Shaun Clowes, and avoiding blind feature copying per Elena Verna. The skill guides war-game style questioning about status quo share, distribution versus feature moats, and competitor iceberg effects where only shipped features are visible. Common mistakes flagged include ignoring no-decision losses, fast-following year-old competitor features, and over-indexing on competitors versus customers. Deep reference material with sixty-three insights lives in references/guest-insights.md with related skills for vision, roadmap, and OKR work.2.7kinstalls3Writing PrdsThe writing-prds skill helps teams write effective product requirements using frameworks from eleven product leaders surfaced in Lenny's Podcast insights. It starts with why the problem matters now, defines success metrics upfront, chooses the right format between traditional docs, prototypes, or executable evals, and keeps documents actionable rather than exhaustive. Core principles include leading with background and urgency, PR FAQ clarity, demos before memos for AI features, evals as living PRDs, lightweight outcome focus, craft-quality artifacts, AI scaffolding for basics, and live interactive PRDs to reduce ambiguity. Coaches ask about customer impact, explicit out-of-scope boundaries, why now timing, and whether a prototype could replace more prose. Common mistakes flagged include solution-first docs, missing success criteria, over-detail developers ignore, static specs where prototypes communicate better, and weak urgency justification. A deep dive reference file holds fourteen guest insights for extended guidance.2.7kinstalls4Brand StorytellingBrand Storytelling helps agents guide users through company narratives for investors, customers, or employees using techniques from Lenny podcast guests and storytelling experts. The workflow clarifies audience and desired action, finds the core transformation or insight, structures the story with proven frameworks, and sharpens memorable phrases and metaphors users can repeat. Principles include leading a movement not just solving a problem, story before product per Brian Chesky, the five-second moment of transformation, starting in the middle of the action, framing problem-solving over success brags, positioning the customer as hero and the founder as mentor, and memification for executive-ready metaphors. Agents ask who the audience is, what transformation sits at the heart, and whether someone could repeat the message at dinner. Common mistakes to flag are company-first openings, feature lists instead of change stories, hero syndrome, vague vision, and missing stakes. A deep dive references guest-insights.md for fifty insights from thirty guests. Use when defining brand strategy, positioning, pitch narratives, or messaging frameworks.2.6kinstalls5Startup IdeationThe startup-ideation skill helps users brainstorm and evaluate startup concepts using frameworks from product leaders featured on Lenny's Podcast. It begins by understanding personal experience, skills, and problems encountered firsthand, then explores whether the information diet is differentiated enough to surface non-obvious opportunities. Core principles emphasize going off the beaten path instead of chasing identical trends, asking what is newly possible today that was not viable yesterday, diversifying information sources, and avoiding idea tarpits in crowded spaces with repeated failures. Coaching questions probe deep personal frustration, unique access, why-now timing, competitive failure history, and billion-dollar feasibility conditions. Common mistakes include trend-chasing without a specific problem, reading the same sources as every other founder, weak timing justification, and attractive tarpit categories with low success rates. A references file holds two guest insights for deeper reading and links to related skills like product-market fit and working backwards.2.6kinstalls6Vibe CodingThe vibe-coding skill helps users create functional software through AI tools and natural language, drawing on product leader insights about prototypes over static mocks. Coaching starts by clarifying the goal, audience, and whether the output is a throwaway prototype, internal tool, or production app. Core principles frame vibe coding as a distinct skill for non-technical roles to ship working code, replacing Figma with thirty-minute functional prototypes, and building tools to build tools such as custom animation editors. Guidance stresses iterative decomposition, testing AI output instead of assuming correctness, and knowing limits where production systems still need professional engineering review. Common mistakes include building everything at once, unclear specifications, expecting production quality from first prompts, and giving up after one attempt. Related skills point to PRDs, usability testing, LLM building, and shipping products. Agents invoke it when users generate code via AI without deep technical background or explore how natural language can produce MVPs and internal utilities quickly.2.4kinstalls7Content MarketingContent Marketing applies frameworks from 23 product leaders to help users design content engines for SEO, brand building, lead generation, or thought leadership. Core principles stress validating Google search demand before writing, treating content as a product with content-market fit, and prioritizing painkiller content over vitamins. Guidance from Camille Ricketts, Meltem Kuran, Lulu Cheng Meservey, Julian Shapiro, and others covers ending the Google search with complete answers, investing in evergreen rewrites, consistency over production value, and AI-assisted rather than fully AI-generated writing. The workflow identifies goals, finds content-market fit for professional anxieties, matches formats to creator strengths, and designs sustainable cadence before chasing virality. Questions probe search demand, painkiller versus vitamin positioning, human voice, and year-long format commitment. Common mistakes flag writing for no demand, keyword stuffing, corporate voice, inconsistent publishing, and missing information gain from human expertise.2.3kinstalls8Giving PresentationsGiving Presentations coaches compelling talks using techniques from nineteen product leaders. Workflow starts with audience, stakes, format, and time, then builds narrative before slide software. Core principles include the bow and arrow method defining one memorable takeaway, Nancy Duarte what is versus what could be contrast, Andy Raskin takeaway slide titles, and mentor-not-hero audience framing. Engagement guidance schedules state changes every three to five slides, uses audience guesses before revealing data, and applies de-risking pre-meetings with stakeholder role-play. Delivery coaching covers looking up when thinking on video, reframing anxiety as excitement, one-to-two breathing ratios, staying in character without leaking nerves, and Accordion Method rehearsal compressing talks to thirty seconds then expanding. Common mistakes flagged include starting in PowerPoint, generic titles, monologue decks without interaction, word-for-word memorization, and apologizing for nervousness. Questions prompt the single remembered sentence, audience cares, contrast story, rehearsal count, objections, and interactive moments. Deep dive references guest-insights.md for forty additional.2.3kinstalls9Ai Product StrategyThe ai-product-strategy skill helps users make strategic decisions about AI products using frameworks distilled from 94 product leaders and practitioners. It starts by understanding what they are building, the problem being solved, and where they are in the AI journey. Core principles include starting with the user problem not the technology, defining human versus algorithm responsibility, treating LLMs as magical duct tape with new cost structures, building for capability slopes not snapshots, and designing for squishiness at sub-perfect accuracy. It guides architecture choices around build versus buy, specialized model societies, evals, observability, and feedback flywheels that improve over time. The skill flags common mistakes such as AI for its own sake, single-model thinking, ignoring failure UX, static architectures, skipping evals, and over-automation. It ends with diagnostic questions about user problems, human-AI boundaries, failure handling, feedback loops, and model improvement trajectories.2.3kinstalls10Analyzing User FeedbackThe analyzing-user-feedback skill helps teams extract actionable insights from customer input across NPS, support tickets, sales notes, social channels, and interviews using frameworks from product leaders. It starts by mapping feedback sources, clustering themes by frequency and impact, and challenging literal complaints to find root causes such as value versus price objections. Core principles include treating feedback as a continuous river, clustering by behavioral pathways instead of demographics, treating support tickets as product failures, weighing silent non-raters, filtering noise from legacy habits, aggregating all channels centrally, interviewing churned users, and prioritizing future users over vocal minorities. The skill asks diagnostic questions about missing channels, churn interviews, underlying patterns, early adopter bias, and planned actions while flagging mistakes like hoarding insights or hindsight bias. A references file holds expanded guest insights, with related skills for interviews, PMF measurement, roadmap prioritization, and OKRs.2.2kinstalls11Founder SalesHelp the user close early customers and codify a repeatable sales process using insights from 16 product leaders When the user asks for help with founder sales 1 Understand their stage Ask how many customers they have whether they have a repeatable ICP and whether they re pre product or have something to demo 2 Diagnose the bottleneck Determine if the problem is lead generation qualification discovery closing or implementation 3 Guide the approach Help them craft outreach prepare for discovery calls or design their sales process based on their specific situation 4 Document for repeatability Encourage them to capture what works so they can eventually hand it off The founder IS the product in early sales Jen Abel Founder led sales is really that first milestone the founder is the product In early stages the founder s novel insight and subject matter expertise are the primary drivers of interest Leverage your status as founder to gain market access Use your ability to see budding moments in conversations to refine2.2kinstalls12Systems ThinkingHelp the user apply systems thinking to complex problems using frameworks and insights from 6 product leaders When the user asks for help with systems thinking 1 Map the system Help them identify all players their incentives and how they interact with each other 2 Identify stocks and flows Understand what accumulates stocks and what moves between states flows 3 Trace second order effects Work through what happens after the first order impact of any change 4 Find leverage points Identify where small interventions can create large systemic changes See the system Seth Godin What does it mean to be a strategic thinker It means to see the system Understanding the invisible rules culture and interoperability that govern how products and organizations succeed or fail is the foundation of strategic thinking2.1kinstalls13Positioning MessagingHelp the user craft compelling product positioning and messaging using frameworks from 58 product leaders and marketers When the user asks for help with positioning and messaging 1 Understand the target audience Ask who specifically they re trying to reach and what those people care about 2 Identify the competitive frame Determine what alternatives customers are comparing them against 3 Find the differentiated value Help them articulate what s uniquely true and valuable about their offering 4 Test message resonance Guide them toward language that reflects how customers describe their own problems Positioning dictates everything Arielle Jackson I really believe that positioning dictates so much of your marketing and should always be the first thing you do I had a student in my last class He goes I ll never write a line of code without doing positioning first Positioning is the foundational element of marketing that should precede product development and all other marketing activities Weak positioning creates pipeline friction April Dunford Weak positioning hurts you in the early2.1kinstalls14Setting Okrs GoalsHelp the user create effective objectives and key results using frameworks and insights from 55 product leaders When the user asks for help with OKRs or goal setting 1 Understand context Ask about their company stage team size and whether they have existing goals or are starting fresh 2 Clarify the level Determine if these are company department team or individual goals 3 Identify the strategy Ensure they have a clear strategy before setting goals goals should be the end of strategy not the beginning 4 Guide the structure Help them write inspiring objectives and measurable key results that avoid common pitfalls Goals should be one step from company goals Matt LeMay No more than one step away from company goals Don t let it get cascaded into oblivion Ensure team goals orbit directly around the primary company objective rather than being buried under layers of organizational cascading Build systems not just goals Lane Shackleton Instead of being obsessed with the goal be obsessed with the system that gets you2kinstalls15Behavioral Product DesignHelp the user apply behavioral science principles to product design using insights from behavioral economists and product leaders When the user asks for help with behavioral design 1 Understand the target behavior Ask what action they want users to take 2 Identify behavioral barriers Help diagnose what s preventing the desired behavior 3 Suggest relevant principles Apply behavioral economics concepts like loss aversion present bias or status quo effect 4 Design interventions Help create features that leverage these psychological principles Loss aversion drives retention Jackson Shuttleworth Once you hit seven days loss aversion kicks in and you retain Design experiences that create something users feel they d lose by leaving Apply psychology to real problems Kristen Berman Behavioral science uses insights on psychology to apply within real world problems biases like present bias status quo effect and uncertainty aversion can be designed into product features to drive specific actions2kinstalls16Sales QualificationHelp the user qualify sales leads effectively using frameworks from 1 product leader When the user asks for help with sales qualification 1 Understand current process Ask how they currently decide which leads to pursue 2 Identify disqualification criteria Help them define what makes a lead NOT worth pursuing 3 Design discovery questions Create questions that efficiently reveal fit 4 Build a qualification framework Help them systematize qualification decisions Most sales problems are qualification problems Jen Abel It s qualification Qualification because if you spend your time on the wrong leads that equates to a zero If conversion rates are low the issue is often pursuing leads that were never going to close rather than poor sales execution No is a successful outcome Jen Abel I am a qualification crazy person I will not get in on another call with someone because on the first call it s either a yes or a no there s no in between The goal of early calls is to determine fit not to2kinstalls17Designing Growth LoopsHelp the user design effective growth loops using frameworks from 54 product leaders who have built viral and product led growth engines at companies from Dropbox to LinkedIn to Calendly When the user asks for help with growth loops 1 Identify the loop type Determine if they need viral paid content or product led acquisition loops 2 Assess prerequisites Check if they have the LTV network effects or product stickiness to support the loop 3 Find the natural sharing moment Help them identify where users would naturally want to bring others in 4 Design for compounding Ensure the loop feeds back into itself for sustainable growth One dominant loop matters most Luc Levesque It s usually just one loop that you need to get right Most successful companies scale primarily through one dominant well executed growth loop Focus on identifying and dominating one primary channel before diversifying Viral growth is a learnable science Nikita Bier With certainty if you re good at your job you can make an app grow1.9kinstalls18Designing SurveysThe designing-surveys skill helps developers and product teams create effective customer surveys, NPS measurements, product-market fit studies, and feedback collection flows using frameworks from nine product leaders. It clarifies survey goals, chooses between CSAT, NPS, PMF, or custom metrics, designs single-variable questions, and targets respondents with fresh relevant experience. Core principles flag NPS scientific flaws in favor of CSAT scales, force prioritization with three-choice constraints, survey best customers within three to six months of signup, and use onboarding friction that improved conversion in real examples. It warns against double-barreled questions, unlimited option lists, wrong timing, NPS worship, and mobile hidden scale options. Deep dive references cover ten guest insights and related skills for North Star metrics, product vision, roadmap prioritization, and OKRs. Use when creating customer surveys, measuring satisfaction, running PMF questionnaires, or improving feedback collection mechanisms before product decisions.1.9kinstalls19Technical RoadmapsThe technical-roadmaps skill. Help users create technical roadmaps. Use when someone is planning engineering work, prioritizing tech debt, building architecture roadmaps, or aligning technical and product strategy. **Understand the context** - Ask about their current technical state, team size, and business constraints 2. **Ensure it's written down** - A strategy that isn't documented can't be debugged or aligned around 3. **Apply the Rumelt framework** - Structure as Diagnosis (what's the problem), Guiding Policies (principles for decisions), and Actions (what you'll do) 4. **Favor boring strategies** - Help them resist the urge to introduce new tools when existing ones would suffice ## Core Principles ### Write it down Will Larson: "The first rule of strategy is that if you write it down, then you can improve it. If it's not written down, it's hard to say if this PM is just not a good PM or if they're trying to apply a strategy they've misunderstood." A written strategy provides a baseline that can be critiqued and improved.1.8kinstalls20Prioritizing RoadmapThe prioritizing-roadmap skill. Help users prioritize product roadmaps and backlogs. Use when someone is deciding what to build next, sequencing features, allocating resources across projects, handling stakeholder requests, or struggling with too many competing priorities. **Understand the decision context** - Ask about their goals, constraints, and stakeholder landscape 2. **Assess the portfolio** - Determine if they need to balance incremental vs big bets, or core vs new 3. **Provide frameworks** - Recommend appropriate prioritization approaches for their situation 4. Where do we have questions?'" Categorize inputs by conviction level vs. questions and rally the team around a shared context. Season one might've been prototyping of AI and then it was all around models and reasoning models, and now it's the advent of agents." In rapidly changing environments, align the team on secular market shifts rather than rigid long-term roadmaps.1.8kinstalls21Design SystemsThe design-systems skill helps developers and design leads build and scale design systems using frameworks from four product leaders at companies like Figma and Airbnb. Workflow assesses consistency versus speed needs, defines scope across components tokens and documentation, designs for adoption so non-designers use the system correctly, and plans evolution with dedicated ownership. Core principles include separating concept from production with low-fidelity block diagrams before high-res comps, design systems as enterprise expansion drivers, assets that teach their own usage through structure, and evolving beyond flat design toward dimensional tactile interfaces. Questions probe inconsistency problems, engineer participation, adoption metrics, maintenance resources, and smallest viable first ship. Common mistakes flag building too early, over-engineering, missing ownership, ignoring adoption, and treating systems as finished. Deep dive references cover four guest insights. Use when creating component libraries, establishing design tokens, scaling brand consistency, or deciding design system investment timing.1.8kinstalls22Career TransitionsHelp users navigate career changes and pivots. Use when someone is considering a new role, transitioning into product management, evaluating job offers, taking a sabbatical, or feeling stuck in their current position. The career-transitions skill documents workflows and patterns from the repository SKILL.md. --- name: career-transitions description: Help users navigate career changes and pivots. Use when someone is considering a new role, transitioning into product management, evaluating job offers, taking a sabbatical, or feeling stuck in their current position. --- # Career Transitions Help the user navigate career changes using frameworks from 76 product leaders who have successfully pivoted roles, industries, and career stages. ## How to Help When the user asks for help with a career transition: 1. **Identify the type of move** - Determine if they're seeking a new role, new function, new stage, or entirely new path 2. **Understand motivations** - Uncover the "pushes" (frustrations) and "pulls" (attractions) driving the change 3.1.8kinstalls23User OnboardingThe user-onboarding skill. Help users design effective product onboarding. Use when someone is creating first-user experiences, trying to improve activation rates, designing the first 30 seconds of product usage, or working on the path to the aha moment. **Understand the aha moment** - Ask what the key value moment is and how quickly users need to reach it 2. **Design the first 30 seconds** - Focus intensely on what happens immediately after signup 3. **Apply game design principles** - Use progressive disclosure and reward mechanics from game design 4. Get users into the core product experience as quickly as possible. The workflow follows the source SKILL.md contract with progressive reference loading, clear trigger phrases, and practical steps developers can apply directly in agent sessions. The workflow follows the source SKILL.md contract with progressive reference loading, clear trigger phrases, and practical steps developers can apply directly in agent sessions.1.8kinstalls24Retention EngagementHelp users improve retention and engagement metrics. Use when someone is dealing with churn, optimizing activation flows, building habit-forming products, or trying to increase user engagement and lifetime value. The retention-engagement skill documents workflows and patterns from the repository SKILL.md. --- name: retention-engagement description: Help users improve retention and engagement metrics. Use when someone is dealing with churn, optimizing activation flows, building habit-forming products, or trying to increase user engagement and lifetime value. --- # Retention & Engagement Help the user improve retention and engagement using frameworks from 29 product leaders. ## How to Help When the user asks for help with retention: 1. **Understand the retention curve** - Ask about their current retention shape and where drop-off occurs 2. **Identify the aha moment** - Help them define what first experience of value looks like for their users 3. **Assess habit formation** - Determine if they're building for habitual vs.1.8kinstalls25Written CommunicationHelp users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive. The written-communication skill documents workflows and patterns from the repository SKILL.md. --- name: written-communication description: Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive. --- # Written Communication Help the user communicate more effectively in writing using frameworks and insights from 38 product leaders. ## How to Help When the user asks for help with written communication: 1. **Clarify the purpose** - Ask what action or outcome they want from readers 2. **Apply the pyramid principle** - Guide them to lead with the conclusion, not build up to it 3. **Cut ruthlessly** - Help them eliminate unnecessary context and get to the point faster 4.1.8kinstalls26Pricing StrategyThe pricing-strategy skill Help users design and optimize pricing strategies. Use when someone is setting prices for the first time, considering freemium vs paid models, optimizing monetization, dealing with willingness to pay questions, or transitioning between pricing models. It covers understand the business model - Ask about their current monetization approach and target customer segments. Key workflows include assess value delivery - Determine what value they're creating and for whom. Developers invoke pricing-strategy when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.1.8kinstalls27Defining Product VisionHelp users create compelling product visions. Use when someone is writing a vision statement, defining a long-term product direction, aligning teams on the future state, or distinguishing vision from strategy. --- name: defining-product-vision description: Help users create compelling product visions. Use when someone is writing a vision statement, defining a long-term product direction, aligning teams on the future state, or distinguishing vision from strategy. --- # Defining Product Vision Help the user create compelling product visions using frameworks from 101 product leaders who have defined visions at companies from Notion to Airbnb to the New York Times. ## How to Help When the user asks for help with product vision: 1. **Clarify the scope** - Determine if they need a vision (long-term aspiration), strategy (how to win), or roadmap (what to build) 2. **Focus on the user's future** - Help them describe the world 5-10 years out, not the product features 3.1.8kinstalls28Problem DefinitionThe problem-definition skill. Help users define problems clearly before jumping to solutions. Use when someone is scoping a new feature, validating a product idea, struggling to articulate what they're building, or falling into the "shiny object trap" with new technology. **Understand the current framing** - Ask how they're currently thinking about the problem 2. **Dig into the struggling moment** - Help them articulate the specific context where users feel stuck 3. **Separate problem from solution** - Ensure they haven't conflated a desired feature with the underlying need 4. **Validate the problem matters** - Help them confirm the problem is urgent and widespread enough to solve ## Core Principles ### Digitizing analog isn't enough Bret Taylor: "Why use this instead of the Yellow Pages?. It was a digital version of something that had come before." Simply digitizing an analog predecessor often fails because it lacks a native reason to exist on the new platform.1.8kinstalls29Usability TestingThe usability-testing skill. Help users conduct effective usability testing. Use when someone is planning user tests, designing prototype validation, preparing usability studies, or trying to understand why users struggle with their product. **Clarify the goal** - Determine if they're validating a concept, finding friction points, or optimizing conversion 2. **Choose the right fidelity** - Help them select between Wizard of Oz tests, fake doors, prototypes, or production testing 3. **Design the test** - Guide them on recruiting users, creating scenarios, and what to observe 4. **Plan for iteration** - Discuss how findings will flow back into the product development process ## Core Principles ### Fake it before you build it Itamar Gilad: "Initially you fake it - fake door test, smoke test, Wizard of Oz tests. We showed the tabbed inbox working to people, but it wasn't really Gmail, it was just a facade." Validate core value propositions before writing production code using faked versions where humans perform the automated task behind the scenes.1.8kinstalls30Conducting User InterviewsHelp users run better customer and user interviews. Use when someone is preparing for user research, planning discovery interviews, writing interview questions, analyzing interview findings, or trying to understand customer needs. The conducting-user-interviews skill documents workflows and patterns from the repository SKILL.md. --- name: conducting-user-interviews description: Help users run better customer and user interviews. Use when someone is preparing for user research, planning discovery interviews, writing interview questions, analyzing interview findings, or trying to understand customer needs. --- # Conducting User Interviews Help the user run better discovery conversations and extract real insights using techniques from 43 product leaders. ## How to Help When the user asks for help with user interviews: 1. **Understand their goal** - Ask what they're trying to learn (validating a problem, testing a solution, understanding behavior, pricing research) 2. **Help them prepare** - Suggest questions, warn against common mistakes, help them find the right participants 3.1.8kinstalls31Writing Specs DesignsThe writing-specs-designs skill. Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams. **Determine the fidelity level** - Ask if they need conceptual alignment (low-fi) or detailed implementation guidance (high-fi) 2. **Encourage prototyping over polish** - Push toward functional prototypes where possible rather than static documentation 3. **Focus on moving pieces** - Help them identify the key affordances, connections, and system behaviors 4. Give me this pen.' It gets you so fast to a shared vision." Drawing 'badly' invites participation and corrections, accelerating alignment. A mock-up doesn't tell you what it's going to feel like." Push for prototypes with real data to test experience, not just static screenshots. Products live and die in the pixels." For zero-to-one products, own the granular design details; every tap is precious.1.8kinstalls32Stakeholder AlignmentStakeholder Alignment helps you navigate internal approval processes and executive decision-making by applying frameworks from 88 product leaders. It teaches you to understand how stakeholders think, not just what they think, and to structure conversations that build trust incrementally. The skill covers pre-alignment strategies, multi-format communication sequences, objection handling, and trade-off framing. Core principles include presenting options with explicit recommendations, securing strategy alignment before planning cycles, and building credibility through consistency. Use this when facing resistance, preparing high-stakes presentations, or influencing without direct authority across cross-functional teams.1.8kinstalls33FundraisingThe fundraising skill helps with Help founders raise capital and build investor relationships. Use when someone is preparing a pitch deck, deciding whether to raise venture capital, meeting with investors, or asking about fundraising strategy. Key workflows include Fundraising Strategy; How to Help; Core Principles; Lead with your strongest point on slide one. Documented capabilities cover "What's your strongest proof point right now - traction, team, insight, or market?"; "Why are you raising venture capital specifically? Have you considered alternatives?"; "What's on your first slide? Is it your strongest point?"; "How many investors have you talked to? What patterns are you seeing in their feedback?"; "What's your target raise and how did you arrive at that number?". Agents should invoke it when users ask about fundraising or mention triggers defined in the skill frontmatter. Follow the SKILL.md steps, reference files, and output formats rather than improvising outside documented scope.1.8kinstalls34Enterprise SalesHelp users navigate enterprise sales. Use when someone is closing large deals, managing complex buying committees, handling procurement, or converting PLG users to enterprise contracts. The enterprise-sales skill documents workflows and patterns from the repository SKILL.md. --- name: enterprise-sales description: Help users navigate enterprise sales. Use when someone is closing large deals, managing complex buying committees, handling procurement, or converting PLG users to enterprise contracts. --- # Enterprise Sales Help the user navigate enterprise sales using frameworks from 9 product leaders who have closed large enterprise deals at companies from Stripe to Superhuman. ## How to Help When the user asks for help with enterprise sales: 1. **Identify the stage** - Determine if they're prospecting, in discovery, navigating procurement, or closing 2. **Map the buying committee** - Help them identify the champion, economic buyer, and other stakeholders 3. **Address indecision** - Focus on overcoming customer fear of messing up, not just building FOMO 4.1.8kinstalls35Ai EvalsAI evals are systematic frameworks for measuring AI product quality, treating evaluation as a core product specification rather than optional testing. This skill guides developers through understanding what success means for their AI features, designing evaluation approaches with appropriate rubrics and test cases, and implementing measurement systems grounded in user needs. The process involves manual review to identify failure patterns, open coding for error classification, and validation of scoring criteria. Evals require discipline: binary Pass/Fail decisions over vague scales, human-validated LLM-as-judge approaches, and iterative refinement based on actual usage patterns. Mastering evals is essential for shipping AI products that reliably meet user expectations.1.7kinstalls36Measuring Product Market FitHelp users assess and achieve product-market fit. Use when someone is trying to determine if they have PMF, measuring user engagement and retention, running the Sean Ellis survey, or figuring out if they should scale or keep iterating. The measuring-product-market-fit skill documents workflows and patterns from the repository SKILL.md. --- name: measuring-product-market-fit description: Help users assess and achieve product-market fit. Use when someone is trying to determine if they have PMF, measuring user engagement and retention, running the Sean Ellis survey, or figuring out if they should scale or keep iterating. --- # Measuring Product-Market Fit Help the user assess and achieve product-market fit using frameworks from 46 product leaders. ## How to Help When the user asks about product-market fit: 1. **Understand their stage** - Ask how many customers they have, what their retention looks like, and what signals they're seeing (or not seeing) 2.1.7kinstalls37Evaluating Trade OffsThe evaluating-trade-offs skill helps with Help users make better decisions between competing options. Use when someone is weighing pros and cons, comparing alternatives, struggling with a difficult choice, deciding between speed and quality, or asking. Key workflows include Evaluating Trade-offs; How to Help; Core Principles; Optimize for order-of-magnitude, not precision. Documented capabilities cover "What are you optimizing for - today, this quarter, or this year?"; "If you weren't already committed to this, would you start it today?"; "What's the full 'all-in' cost of each option, including maintenance and opportunity cost?"; "Is this decision reversible or a one-way door?"; "Who loses if you choose option A? Is that trade-off acceptable?". Agents should invoke it when users ask about evaluating trade offs or mention triggers defined in the skill frontmatter. Follow the SKILL.md steps, reference files, and output formats rather than improvising outside documented scope.1.7kinstalls38Launch MarketingThe launch-marketing skill Help users plan and execute product launches. Use when someone is planning a product launch, preparing PR outreach, coordinating a go-to-market campaign, launching on Product Hunt, or asking how to generate buzz for a new feature or product. It covers understand the launch type - Ask whether this is a company launch, funding announcement, major feature, or incremental release. Different types require different approaches. Key workflows include clarify goals - Determine the primary objective: customer acquisition, recruiting, fundraising, feedback, or partnership opportunities. Developers invoke launch-marketing when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.1.7kinstalls39Community BuildingThe community-building skill Help users build and grow product communities. Use when someone is starting a community, scaling an ambassador program, driving community-led growth, or choosing between user, developer, or partner communities. It covers identify the community type - Clarify if they need a user community, agency community, or partner community. Key workflows include find the atomic unit of sharing - Determine what community members would naturally want to show off. Developers invoke community-building when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.1.7kinstalls40Product Led SalesThe product-led-sales skill Help users implement product-led sales motions. Use when someone is transitioning from pure PLG to sales-assisted, defining PQLs, building sales handoff processes, or trying to expand self-serve users into enterprise contracts. It covers understand the current state - Ask about their existing PLG motion and sales infrastructure. Key workflows include define the trigger criteria - Help them identify what signals indicate a user is ready for sales outreach. Developers invoke product-led-sales when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.1.7kinstalls41Building With LlmsThe building-with-llms skill Help users build effective AI applications. Use when someone is building with LLMs, writing prompts, designing AI features, implementing RAG, creating agents, running evals, or trying to improve AI output quality. It covers understand their use case - Ask what they're building chatbot, agent, content generation, code assistant, etc.. Key workflows include diagnose the problem - Help identify if issues are prompt-related, context-related, or model-selection related. Developers invoke building-with-llms when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.1.7kinstalls42Design EngineeringDesign engineering merges UX design with production engineering to accelerate prototyping and shipping. This skill helps teams define the role's scope, assess hiring versus upskilling, and position design engineers organizationally. Core frameworks from leaders at Snap, Captions, and Vercel emphasize combining design sensibility with shipping capability. Key challenges include clarifying whether design engineers prototype or ship production code, avoiding isolated org placement, and hiring for strength at the intersection rather than unicorn mastery. The role becomes increasingly accessible via AI-assisted development tools.1.7kinstalls43Running Decision ProcessesRunning Decision Processes equips users with frameworks and principles from 65 product leaders to execute effective decision-making workflows. The skill helps distinguish between reversible and irreversible decisions, identifies decision blockers (analysis paralysis, lack of ownership, implicit assumptions), and recommends appropriate frameworks like DACI to clarify accountability. Core principles include making implicit reasoning explicit, using curiosity loops for stakeholder advice, acting as a historian to learn from past decisions, and recognizing when high-conviction decisions require leaps of faith despite incomplete data. Users learn to commit fully once decided and avoid relitigating settled choices, transforming organizational hesitation into decisive action.1.7kinstalls44Product OperationsProduct operations bridges product teams with organizational operations, creating systems that enable scaling without bureaucracy. The function handles enablement, release management, and insight standardization so product managers focus on strategy. This skill draws from five product leaders: Brian Tolkin, Christine Itwaru, Geoff Charles, Melissa Perri, and Denise Tilles. It addresses the specific pain points that emerge when product orgs grow: fragmented processes, delayed insights, and operational tasks consuming PM time. Use this when scaling product teams, establishing cross-functional coordination, or standardizing how data reaches decision makers.1.7kinstalls45Startup PivotingThe startup-pivoting skill helps with Help users decide when and how to pivot their startup. Use when someone is questioning their current direction, seeing poor traction, considering a major strategy change, or stuck in the pre-PMF stage. Key workflows include Startup Pivoting; How to Help; Core Principles; Have you exhausted the possibilities?. Documented capabilities cover "What have you tried so far, and what did you learn from each attempt?"; "If you were an outside investor looking at this company, what would you conclude?"; "Is this a tweak to your current approach or a fundamental rethink?"; "Which of the Four Ps (Problem, Persona, Product, Positioning) might be wrong?"; "What would a 200% pivot look like compared to what you're considering?". Agents should invoke it when users ask about startup pivoting or mention triggers defined in the skill frontmatter. Follow the SKILL.md steps, reference files, and output formats rather than improvising outside documented scope.1.7kinstalls46Building A Promotion CaseThe building-a-promotion-case Lenny skill coaches users preparing promotion conversations with frameworks from product leaders. Agents clarify target level expectations, document impact with metrics and scope growth, identify sponsorship and advocacy gaps, and structure a narrative connecting past results to next-level responsibilities. It addresses common blockers such as unclear leveling rubrics, missing executive visibility, and weak documentation of cross-team influence. Guided questions probe what evidence hiring managers need, which projects demonstrate scope expansion, and how to align with calibration timelines. Use when users prepare promotion packets, manager reviews, or career leveling discussions. Frames promotion evidence around level expectations and impact metrics. Identifies sponsor alignment and advocacy gaps. Structures narrative from results to next-level scope. Addresses calibration timing and visibility blockers. Coaches advancement conversations with Lenny guest patterns. Build a promotion case with impact evidence, level expectations, sponsor alignment, and narrative for advancement conversations.1.7kinstalls47Writing North Star MetricsThe writing-north-star-metrics skill helps with Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy. Key workflows include Writing North Star Metrics; How to Help; Core Principles; Measure value delivered, not captured. Documented capabilities cover "What specific moment represents a user getting value from your product?"; "Could a non-technical person in your company understand and discuss this metric?"; "Can teams actually influence this metric through their work in a quarter?"; "What would happen if you gamed this metric - what would break?"; "Does this metric measure value delivered to users or value extracted from them?". Agents should invoke it when users ask about writing north star metrics or mention triggers defined in the skill frontmatter. Follow the SKILL.md steps, reference files, and output formats rather than improvising outside documented scope.1.7kinstalls48Product Taste IntuitionThe product-taste-intuition skill helps with Help users develop product taste and intuition. Use when someone wants to improve their product judgment, struggles to evaluate design quality, needs to make decisions without complete data, or wants to build better product instincts. Key workflows include Product Taste & Intuition; How to Help; Core Principles; Intuition is a hypothesis generator. Documented capabilities cover "What products do you use daily that you think are exceptionally well-designed? What makes them great?"; "When was the last time you analyzed a competitor's product in detail? What did you learn?"; "When you use a new app, what do you notice first? What bothers you?"; "How often do you experiment with products outside your industry or domain?"; "When your intuition and data conflict, how do you decide what to do?". Agents should invoke it when users ask about product taste intuition or mention triggers defined in the skill frontmatter. Follow the SKILL.md steps, reference files, and output formats rather than improvising outside documented scope.1.7kinstalls49Conducting InterviewsThe conducting-interviews skill helps with Help users conduct effective hiring interviews. Use when someone is designing an interview loop, crafting interview questions, evaluating candidates in real-time, or building a structured interview process. Key workflows include Conducting Interviews; How to Help; Core Principles; Use behavioral-based interviewing. Documented capabilities cover "What competencies are most critical for this specific role?"; "Are you testing for skills that can be rehearsed or genuine capability?"; "How will you distinguish between confident delivery and quality thinking?"; "What signals true ownership versus 'we' statements that hide contribution?"; "How are you calibrating across multiple interviewers?". Agents should invoke it when users ask about conducting interviews or mention triggers defined in the skill frontmatter. Follow the SKILL.md steps, reference files, and output formats rather than improvising outside documented scope. When the user asks for help with conducting interviews: 1. **Understand the role** - Ask what position they're hiring for and what competencies matter most 2. **Design the structure** - Help create a consistent, behavioral-ba.1.6kinstalls50Planning Under UncertaintyThe planning-under-uncertainty skill helps with Help users plan products and strategy when outcomes are unpredictable. Use when someone is dealing with ambiguous timelines, building in fast-moving markets, planning AI/ML projects, or asking how to make commitments when they don't know what will happen. Key workflows include Planning Under Uncertainty; How to Help; Core Principles; Embrace optionality over prediction. Documented capabilities cover "What would need to be true for your current plan to work? Which of those assumptions are you least confident about?"; "If this takes twice as long as expected, what would you do differently? What if it takes half as long?"; "What's the smallest thing you could ship to learn whether your core hypothesis is correct?"; "Is this a one-way door or a two-way door decision?"; "What signals would tell you to pivot or kill this initiative?". Agents should invoke it when users ask about planning under uncertainty or mention triggers defined in the skill frontmatter. Follow the SKILL.md steps, reference files, and output formats rather than improvising outside1.6kinstalls51Managing UpThe managing-up Lenny skill helps ICs and managers improve executive relationships with structured updates, proactive alignment, and influence without authority. Frameworks cover expectation setting, bad-news delivery, and building trust with skip-level stakeholders. Agents coach on communication cadence, decision framing, and when to escalate. Use when users struggle with manager dynamics or executive visibility. Structured updates and proactive alignment patterns. Influence without authority frameworks. Expectation setting and escalation guidance. Trust building with managers and executives. Lenny guest coaching for managing up. Work effectively with managers and executives through influence, communication, and trust-building.1.6kinstalls52Running Design ReviewsThe running-design-reviews skill from Lenny's Podcast collection helps teams run design critiques using frameworks from eight product leaders. Agents clarify review context, establish a feedback hierarchy prioritizing value, usability, then delight, structure constructive critique requests, and define what good enough to ship means. Core principles include assigning sponsors for major projects, reviewing every shipped screen, starting big picture before pixel details, and using blurred-vision cohesion checks. The skill flags mistakes such as unstructured feedback, static slide reviews, and aesthetic opinions before value validation. Guided questions target specific feedback types, core value clarity, highest-risk elements, and shippability thresholds. It references guest insights and related skills like product taste intuition and running effective meetings. Use when giving design feedback, establishing review processes, struggling to evaluate designs, or improving how teams discuss interface work before release.1.6kinstalls53Post Mortems RetrospectivesThe post-mortems-retrospectives skill applies frameworks from eleven Lenny Podcast leaders to turn project outcomes into actionable learning. It distinguishes failure, success, and routine checkpoints, emphasizes blameless psychological safety, and uses pre-mortem kill criteria from Annie Duke. Reframing retrospectives positively, institutionalizing weekly impact and learnings reviews, and grading OKRs for why not what percentage are core themes. Agents ask about ignored early signals, systemic contributors, and follow-through mechanisms. Mistakes flagged include blame framing, no action on learnings, success-only reviews, score obsession, and one-off events. Use after project success or failure, when establishing team learning loops, or improving decision quality over time.1.6kinstalls54Working BackwardsThe working-backwards skill coaches teams to start from customer problems, draft mock press releases, develop internal FAQs, and test whether ideas are big enough, strategically fit, and have viable plans. Frameworks from twelve Lenny Podcast leaders cover backcasting from a five-year future, defining theoretical ideal outcomes, and aligning GTM machinery beyond product specs. Agents flag retrofitting problems onto pre-chosen solutions, vague benefits, skipped FAQs, incremental-only thinking, and product-only scope. Questions elicit customer wording, headline quotes, elephant-in-the-room FAQs, and ideal-state definitions. Use when defining new products, writing PR/FAQ documents, planning from future state, or clarifying value propositions before implementation.1.6kinstalls55Platform StrategyThe platform-strategy skill from Lenny's Podcast collection guides marketplace, API, ecosystem, and developer platform decisions using insights from twenty-four leaders. Agents clarify platform type, identify network effects between sides, assess moat-building versus opening versus closing lifecycle stages, and design governance rules. Principles include treating internal platforms as products, reducing cognitive load via clear interfaces, finding compounding dynamics, building systems not features, and investing incrementally on adoption signals. Questions probe cold-start value, supply commoditization risk, and dispute handling. It flags building in a vacuum, skipping moat phases, and over-investing before utility signals. Use when building marketplaces, planning API strategy, or designing multi-sided network businesses.1.6kinstalls56Coaching PmsThe coaching-pms Lenny skill helps leaders develop PMs via explicit definitions of good, current assessments, shared growth vision, development plans, and follow-up accountability. Frameworks cite Petra Wille competency models, Bangaly Kaba Bloom taxonomy levels from knowledge through evaluation, and Marty Cagan emphasis on coaching as primary leadership work. Questions probe stage-specific competencies, biggest gaps, and leader time spent coaching versus doing. Mistakes include coaching without models, identical treatment of junior and senior PMs, weakness-only focus, delegating development to HR, and skipping follow-up. Use when managing PMs, writing development plans, running performance reviews, or leveling PM team capabilities.1.6kinstalls57Cross Functional CollaborationThe cross-functional-collaboration skill applies insights from fifty-seven Lenny guests on PM-engineering-design partnerships. Principles include generous credit sharing, yes-and dual-goal thinking, written expectations contracts revisited quarterly, engineer participation in discovery, avoiding telephone PM roles, daily engineer pairing, personal relationship building, code-as-common-language prototypes, and Teresa Torres product trios resolving conflicts with data not rank. Agents diagnose friction type, clarify expectations, recommend team structures, and emphasize human connection questions like career goals and milestones. Mistakes flagged include credit hoarding, excluding engineers from ideation, unclear boundaries, and ignoring personal rapport. Use when navigating cross-team conflict, building trios, or improving handoffs.1.6kinstalls58Building Sales TeamThe building-sales-team Lenny skill guides hiring first salespeople and leaders using frameworks from fourteen guests. Core rules require founder win-rate proof around fifteen to twenty-five percent from fifty to one hundred at-bats before hiring, always hiring two reps for A-B testing, delaying sales until Series A experimentation completes, matching grower versus hunter profiles to inbound PLG versus outbound motions, and hiring VP sales only after two reps hit quota. Early sellers should cosplay founders with vision selling; technical companies expect AE product fluency passing a ten-engineer PM test. Product-led sales pilots should attach experimental AEs outside quota pressure initially. Use when hiring first sales, structuring compensation, or transitioning from founder-led closing.1.6kinstalls59Platform InfrastructureThe platform-infrastructure Lenny skill guides internal and shared technical platform decisions using insights from five leaders. Themes include abstracting repetitive capabilities like columnar features into shared layers, investing in invisible reliability and privacy qualities, planning scale before doomsday spikes, embedding discoverability in large architectures, and defaulting analytics to server-side tracking. Agents ask who platform users are, current developer pain, adoption metrics, build versus buy timing, and infrastructure doomsday clocks. Mistakes include abstract future-only platforms, missing product ownership, ignoring migration costs, and client-side analytics defaults. Use when deciding build versus buy tooling, designing developer platforms, or managing technical debt at scale.1.6kinstalls60Managing TimelinesThe managing-timelines skill from Lenny's Podcast helps teams set and hit realistic deadlines using insights from thirteen product leaders. Agents diagnose estimation versus scoping versus distraction issues, then apply phase-based commitments, hill chart uncertainty tracking, early shipping at ten percent time, and manufactured momentum milestones. Core principles treat real external deadlines as P0, commit to discovery and solutioning phases before distant delivery dates, ship early to iterate with remaining time, and use weekly RAG reviews to unblock stalled work. It flags committing before discovery, too many competing P0 deadlines, front-loading estimation over shipping, planning fallacy underestimation, and asking for extensions instead of building buffers. Guided questions probe external versus internal commitments, current work phase, hidden estimate padding, and focused work time. Use when planning timelines, missing deadlines, or calibrating estimation accuracy with stakeholders.1.6kinstalls61Organizational DesignThe organizational-design skill helps teams choose structures using insights from product leaders on the speed versus coherence trade-off. Amazon-style decentralization minimizes dependencies for parallel execution; Apple-style centralization optimizes integrated product experience through coordination. Brian Chesky functional model guidance restores startup speed by eliminating divisional layers and telephone-game management. Principles flag reorgs without clear problems, copying prestige structures, excessive management layers, and leaders who cannot review actual output. Agents probe what problem restructuring solves, optimization for independent speed or product coherence, layers between executives and ICs, and coordination failures. Use when planning reorgs, choosing functional versus divisional models, or structuring product teams. Fundamental trade-off: decentralized speed versus centralized coherence. Functional models can restore startup speed per Brian Chesky. Eliminate managers who cannot review team output. Structure should follow strategy, not copy prestige org charts.1.6kinstalls62Scoping CuttingThe scoping-cutting skill helps teams define MVPs and cut scope using frameworks from fifteen product leaders. Agents clarify the hypothesis, appetite budget, essential core, and learning goals before recommending cuts. Principles include Ryan Singer appetite over estimates, Eric Ries MVP as validation tool, aggressive halving of feature lists twice, Jason Fried six-week two-person appetite, and Eeke de Milliano scooter-not-axle end-to-end slices. Wizard of Oz manual validation precedes automation when faster. Projects still uphill at time limit should die rather than extend. Flags cover estimating instead of time-boxing, building incomplete axles, never killing overdue work, and skipping manual validation. Use when defining MVP, fighting scope creep, or making tradeoffs about what to ship first. Uses appetite time budgets instead of open-ended estimates. Cuts MVP feature lists in half twice before building.1.6kinstalls63Evaluating CandidatesThe evaluating-candidates skill from Lenny's Podcast guides hiring decisions using frameworks from ninety-four product leaders. Agents clarify screening stage, role context, and decision type, then apply principles prioritizing reference checks over interview signals, team balance over unicorn hires, and paid two-to-three day work trials for operational fit. Structured evaluation completes rubrics before intuition, seeks world-class strengths over absence of weaknesses, and uses Bar Raiser debriefs with veto power. It probes agency and clock speed over pedigree, T-shape depth with gap coverage plans, and mission alignment for retention. Flags include pedigree shortcuts, unstructured gut decisions, and ignoring behavior outside formal interviews. Use when reviewing finalists, calibrating hiring bar, conducting references, or evaluating work samples and take-home exercises. Prioritizes reference checks over short interview signals. Uses paid two-to-three day work trials for operational fit.1.6kinstalls64Shipping ProductsThe shipping-products skill from Lenny's Podcast helps teams ship effectively using insights from forty-seven product leaders. Agents identify blockers such as scope, quality fears, dependencies, or org friction, assess new product versus iteration context, challenge timelines with maximally accelerated critical path thinking, and balance speed with product-appropriate quality bars. Principles include speed as craft signal, ship for feedback, smaller changes improving stability, ninety-nine percent done equals zero value until launch, ask why not ship tomorrow, Product Quality List checklists, ship to learn then polish, tempo over org design, and compound velocity gains from one-week shipping improvements. Use when planning launches, struggling to release, improving shipping velocity, or establishing release practices. Speed plus quality signals mastery not sloppiness. Ship early to accelerate feedback loops. Smaller frequent releases reduce blast radius. 99% done delivers zero customer value until launched.1.6kinstalls65Energy ManagementThe energy-management skill helps users sustain performance by managing energy not just time using frameworks from five product leaders. Agents diagnose energy drains versus drivers, audit calendars categorizing tasks by energy impact, design work around superpowers, and build sustainable rhythms with recovery time. Principles include scheduling for energy levels, identifying moments that add versus subtract energy per Bob Moesta, categorizing calendar buckets and cutting bottom tiers per Claire Vo, and using superpowers to generate energy per Donna Lichaw. Post-activity energy tracking after calls and tasks guides career direction per Paul Millerd. Flags ignoring energy signals, over-optimizing calendar slots without energy context, avoiding delegation, and back-to-back draining work. Use when feeling burned out, finding zone of genius, or scheduling for productivity. Schedule for energy levels not just calendar time slots. Identify energy drivers versus drains from real activities.1.6kinstalls66Having Difficult ConversationsThe having-difficult-conversations skill helps users prepare and deliver hard conversations with frameworks from 43 product leaders. Workflow understands conversation type (feedback, performance, firing, conflict, denied promotion), checks preparation for specific examples and desired outcomes, selects SBI, CORE, NVC, or Radical Candor structures, and offers role-play practice. Core principles include Kim Scott's Radical Candor (care personally and challenge directly), Paige Costello's Situation-Behavior-Impact objectivity, and avoiding ruinous empathy that withholds helpful feedback. Agents ensure camera-recordable behaviors are cited rather than motive assumptions. Use when giving hard feedback, performance conversations, firings, colleague conflict, or delivering disappointing news. Frameworks: SBI, CORE, NVC, and Radical Candor matched to situation type Preparation check for specific examples, outcomes, and other person's perspective Role-play option to rehearse tone and anticipate reactions Radical Candor balances care personally with challenge directly SBI keeps feedback objective: situation, behavior, impact having-difficult-conversations guides tough feedback and conflict.1.6kinstalls67Writing Job DescriptionsThe writing-job-descriptions skill applies frameworks from six product leaders to help users craft postings that attract the right candidates. Workflow defines success first by asking what changed in the business twelve months after the hire, identifies the one or two spike areas where the person must excel, frames the role around progress to be made rather than made-up task lists, and considers whether language signals inclusion or repels strong fits. Core principles include Jonathan Lowenhar's champagne test for year-one impact, Bob Moesta's view that JDs are invented lists managers want, and writing for progress over feature requirements. Use when creating job postings, defining new roles, preparing to hire, or improving candidate quality for open positions. Starts with 12-month success definition, not arbitrary responsibility bullets Identifies one or two spike strengths the hire must excel at Frames roles around progress enabled rather than feature checklists Reviews whether posting language attracts or repels target candidates Draws on six product leader frameworks for hiring clarity writing-job-descriptions helps craft job postings centered on year-one1.6kinstalls68Managing Tech DebtThe managing-tech-debt skill applies insights from 18 product leaders to help users handle legacy code, refactoring plans, rewrite vs incremental decisions, and balancing features with maintenance. Workflow diagnoses debt type (legacy systems, code quality, architecture limits), urgency (velocity drops, incidents, shipping blocks), and recommends incremental improvement, targeted refactoring, or rarely full rewrite. Camille Fournier warns rewrites underestimate migration time while supporting old systems. Ebi Atawodi frames infrastructure as product debt PMs must own in top problems lists. Use when planning refactors, seeking buy-in, or deciding rewrite vs uplift. Diagnoses debt type, business impact, and urgency before recommending approach Prefers incremental uplift over full rewrites per leader guidance Builds business case quantifying cost of debt for stakeholders Frames tech debt as product debt PMs must co-own Insights from 18 product leaders on maintenance vs feature balance managing-tech-debt helps prioritize refactoring and maintenance with business-aligned incremental strategies Chosen approach with business case, urgency diagnosis, and stakeholder narrative User deals w.1.6kinstalls69Evaluating New TechnologyThe evaluating-new-technology Lenny skill helps teams assess new tools, AI vendors, and architecture options before commitment. Frameworks cover problem-solution fit, integration cost, operational burden, vendor lock-in, security review, and experiment design for proof-of-value. Agents structure comparison matrices, pilot scopes, and decision timelines rather than hype-driven adoption. Questions target failure modes, team skill gaps, migration paths, and measurable success criteria for trials. Mistakes include evaluating features without workflow fit, skipping total cost of ownership, and conflating demos with production readiness. Use during tool selection, AI vendor RFPs, or build-versus-buy architecture decisions. Build-versus-buy and vendor evaluation frameworks. Pilot scope and measurable success criteria for trials. Covers integration cost, lock-in, and security review. Structures comparison matrices instead of hype-driven picks. Lenny guest patterns for emerging technology decisions. Evaluate emerging tools and AI vendors with build-versus-buy criteria, risk assessment, and architecture fit.1.6kinstalls70Running Effective MeetingsThe running-effective-meetings Lenny skill reduces meeting overload with frameworks for purpose, attendees, agenda design, decision capture, and async alternatives. Agents clarify whether a meeting is needed, define desired outcomes, assign decision owners, and structure timeboxed discussion flows. Core principles include defaulting to async updates, inviting only decision stakeholders, and ending with documented actions and owners. Mistakes cover status meetings without decisions, missing pre-reads, and unclear next steps. Use when users struggle with meeting culture, prepare high-stakes sessions, or need help driving decisions in group settings. Clarifies meeting purpose, outcomes, and decision rights. Structures agendas and timeboxed discussion flows. Defaults to async alternatives when appropriate. Captures actions, owners, and follow-up accountability. Lenny guest patterns for healthier meeting culture. Run meetings with clear outcomes, decision rights, agendas, and follow-up accountability from Lenny Podcast leaders.1.6kinstalls71Partnership BdThe partnership-bd Lenny skill guides business development for strategic partnerships, platform deals, and distribution agreements. Agents clarify mutual value, negotiation levers, partnership structures, and success metrics. Frameworks address Google or Facebook style platform partnerships and long-tail integrator deals. Use when pursuing BD opportunities or designing partner programs. Strategic partnership and BD deal frameworks. Mutual value and negotiation lever analysis. Platform and distribution partnership patterns. Success metrics for partner programs. Lenny guest business development guidance. Build strategic partnerships and BD deals with platform partners and distribution channels. Structured deliverables and steps from the partnership-bd skill workflow. User mentions partnership-bd or related skill triggers from the description. How do I apply partnership-bd for the workflow described in SKILL.md?. Teams using partnership-bd as documented in the skill repository. Help users build strategic partnerships and business development deals.1.6kinstalls72Delegating WorkThe delegating-work Lenny skill helps leaders decide what to delegate, set outcome-based briefs, choose autonomy levels, and coach without micromanaging. Frameworks address trust building, escalation paths, and balancing hands-on involvement with team growth. Agents identify tasks suitable for delegation, define success metrics, and plan check-in cadences. Use when managers struggle to let go, need delegation frameworks, or want to build team autonomy. Outcome-based delegation briefs and autonomy levels. Coaching without micromanagement patterns. Identifies delegatable tasks and success metrics. Trust building and escalation path guidance. Lenny guest frameworks for effective delegation. Delegate effectively with clear outcomes, autonomy levels, coaching, and letting go of hands-on control. Structured deliverables and steps from the delegating-work skill workflow. User mentions delegating-work or related skill triggers from the description. How do I apply delegating-work for the workflow described in SKILL.md?.1.6kinstalls73Negotiating OffersThe negotiating-offers Lenny skill coaches compensation negotiations covering salary, equity, signing bonus, role scope, and start date tradeoffs. Agents help users research market bands, identify leverage, practice ask scripts, and evaluate total package value beyond base pay. Frameworks address when to negotiate, how to counter professionally, and what concessions are reasonable. Use before accepting offers or preparing compensation conversations. Salary, equity, and total package negotiation coaching. Market band research and leverage assessment. Counter-offer scripts and professional framing. Tradeoffs across bonus, scope, and start date. Lenny guest patterns for offer negotiations. Negotiate job offers on salary, equity, and terms with preparation scripts and leverage assessment.1.6kinstalls74Organizational TransformationThe organizational-transformation skill helps shift toward modern product practices using insights from Marty Cagan and John Cutler. Diagnoses feature-team output focus waterfall starting points readiness authority and resistance. Principles: frameworks are means not ends transform via pilot empowered teams then spread nudge legacy companies carefully change structure culture and process together not one dimension. Use shifting feature teams to product teams introducing empowered teams modernizing legacy processes or driving how product is built with measurable pilot success before broad rollout. Frameworks are means not ends. Pilot empowered teams then spread. Nudge legacy without systemic rejection. Structure culture process change together. Marty Cagan transformation techniques. Org transformation to product operating model. User asks organizational transformation product model.1.6kinstalls75Onboarding New HiresThe onboarding-new-hires skill helps leaders onboard using 14 product leader approaches. Clarifies onboarding versus being onboarded seniority new-role versus backfill then structures 30-60-90 plans with milestones success criteria belonging learning and early wins. Principles include listen-first diagnosis prioritizing social integration engineering quick value demonstration and avoiding task-only ramps. Use planning new hire ramp first-month experiences or coaching managers on effective onboarding for product engineering teams remote or in-person with measurable success criteria. 30-60-90 milestones and success criteria. Belonging and social integration with tasks. Engineer early wins quickly. Listen-first before prescribing steps. 14 product leader approaches. Lenny onboarding skill. User asks onboarding new hires.1.6kinstalls76Building Team CultureThe building-team-culture skill helps leaders sustain culture using insights from 138 product leaders. It diagnoses definition, communication, or enforcement gaps, articulating what works instead of inventing aspirational values. Principles include articulate-don't-create, culture guiding decentralized decisions, coaching over management, earning trust before change, challenging sacred cows, and culture as talent magnet. Agents ask about team size, remote context, failure responses, and flag values without behaviors. Use when defining team values, onboarding, navigating cultural change, or building distributed norms with psychological safety enabling honest feedback across startups and large tech companies. Articulate existing culture not aspirational slogans. Culture guides decisions when leadership absent. Coaching over task oversight. Flags values without behaviors. 138 leader insights with hiring-related skills. Lenny skill for team culture articulation. User asks about team culture or psychological safety.1.6kinstalls77Engineering CultureThe engineering-culture skill builds high-performing engineering orgs using frameworks from 19 leaders. It diagnoses DevEx, org structure, talent, or process bottlenecks. Principles include DevOps as capabilities not toolchains, Conway's Law mapping org to architecture, DevEx pillars of flow state cognitive load and feedback loops, clock-speed shipping, all functions touching code, talent density reducing process, and pair programming for elegant solutions. Agents flag tool-buying over capability building, ignoring Conway's Law, neglecting DevEx, over-processing excellent teams, and code quality over customer value. Use when improving developer experience, scaling engineering organizations, or designing technical practices for speed and stability. DevOps as capabilities not purchased tools. Conway's Law links org to architecture. DevEx: flow, cognitive load, feedback loops. Pair programming for knowledge transfer. Clock-speed frequent ship and test culture. Engineering culture and DevEx improvement skill. User asks about engineering culture or DevEx.1.6kinstalls78Sales CompensationThe sales-compensation skill designs effective sales compensation using Jason Lemkin and Sahil Mansuri frameworks. Understands sales cycle ACV retention patterns misaligned incentives ramp and quotas. Principles include 50/50 OTE baseline modern plans aligning business customer rep incentives retention-weighted components not just bookings ramp draws 3-12 months simplicity over gaming. Use hiring first sales rep restructuring comp aligning incentives or fixing sandbagging churn from misaligned commission structures. 50/50 OTE common baseline. Align comp with retention not just bookings. Ramp periods 3-12 months by segment. Simplicity beats complex gaming plans. Modern plans align business customer rep. Sales compensation design skill. User asks sales compensation or quotas.1.5kinstalls79Running Effective 1 1sThe running-effective-1-1s skill helps run one-on-one meetings using frameworks from 7 product leaders. Understand relationship role report tenure dynamics identify whether focus is tactical work career development or emotional support suggest formats coach shifting from advising to empowering reports. Rachel Lockett principle great leaders coach not always advise. Use improving manager-report 1:1 structure career conversations or emotional support sessions for product and engineering leads. Coach don't advise as core principle. Clarify tactical career or support focus. Formats based on relationship context. 7 product leader 1:1 frameworks. Empower reports don't always have answers. Effective 1:1 meetings skill. User asks effective 1:1s one-on-ones.1.5kinstalls80DogfoodingThe dogfooding skill Help users implement effective dogfooding practices. Use when someone is trying to get their team to use their own product, designing internal usage programs, or building user empathy through personal product use. Documentation covers workflows, commands, and guardrails agents should follow when users invoke this capability. Key documented areas include **Assess current state** - Determine how much the team currently uses their own product; **Identify the gap** - Find where team members lack firsthand experience with user pain points; **Design the program** - Help create systems that make dogfooding natural and required; **Measure impact** - Track how dogfooding improves product decisions. Use when developers or agents need structured guidance for dogfooding tasks with evidence grounded in the bundled SKILL.md rather than generic advice. **Assess current state** - Determine how much the team currently uses their own product **Identify the gap** - Find where team members lack firsthand experience with user pain points **Design the program** - Help create systems that make dogfooding natural and required **Measure impact**1.5kinstalls81Managing Imposter SyndromeThe managing imposter syndrome skill Help users work through feelings of inadequacy and self-doubt. Use when someone feels like a fraud, doubts their qualifications, is anxious about being "found out," or struggling with confidence in a new or challenging role. Documentation covers workflows, commands, and guardrails agents should follow when users invoke this capability. Key documented areas include **Normalize the experience** - Help them understand that imposter syndrome is nearly universal among high performers, especially during growth periods; **Reframe the discomfort** - Connect their uncomfortable feelings to evidence that they're growing and being challenged appropriately; **Identify the specific fear** - Help them articulate exactly what they're afraid of (being exposed, making mistakes, not belonging); **Build practical strategies** - Develop tactics for managing the feelings when they arise. Use when developers or agents need structured guidance for managing imposter syndrome tasks with evidence grounded in the bundled SKILL.md rather than generic advice.1.5kinstalls82Marketplace LiquidityThe marketplace liquidity skill Help users build and manage marketplace liquidity. Use when someone is working on a marketplace business, struggling with supply/demand balance, trying to improve match rates, or asking how to reach critical mass in a two-sided market. Documentation covers workflows, commands, and guardrails agents should follow when users invoke this capability. Key documented areas include **Understand the marketplace type** - Ask about their supply/demand dynamics, how fragmented the market is, and whether needs are uniform or heterogeneous; **Diagnose the constraint** - Determine if they're supply-constrained, demand-constrained, or facing a matching problem; **Define liquidity metrics** - Help them establish clear measures of marketplace reliability and fill rates; **Design interventions** - Guide them on where to focus to improve liquidity (geographic focus, supply acquisition, demand generation, matching quality). Use when developers or agents need structured guidance for marketplace liquidity tasks with evidence grounded in the bundled SKILL.md rather than generic advice.1.5kinstalls83Media RelationsThe media relations skill Help users build relationships with journalists and get press coverage. Use when someone is pitching reporters, preparing for media outreach, trying to get press coverage, or managing ongoing journalist relationships. Documentation covers workflows, commands, and guardrails agents should follow when users invoke this capability. Key documented areas include **Understand their goal** - Ask what kind of coverage they're seeking (launch announcement, thought leadership, feature story) and what stage they're at; **Prepare the story** - Help them craft a compelling angle that's newsworthy, not just promotional; **Identify the right targets** - Guide them on finding the right reporters and publications for their story; **Execute the pitch** - Help them write effective pitches and manage the outreach process. Use when developers or agents need structured guidance for media relations tasks with evidence grounded in the bundled SKILL.md rather than generic advice.1.5kinstalls84Finding Mentors SponsorsThe finding-mentors-sponsors skill helps users build mentor and sponsor relationships using approaches from 19 product leaders in the Lenny's Podcast corpus. It starts by clarifying whether the user needs advice from a mentor, advocacy from a sponsor, or accountability from a coach, because each relationship needs a different outreach strategy. Agents guide candidate identification toward people two to three years ahead on the desired path or with organizational influence, then design small specific asks instead of awkward formal mentor requests. Core principles include differentiating sponsors who bet professional capital from mentors who give advice, starting with two-minute email questions, building a stable of multiple mentors on rotating schedules, and always closing the loop with results. Common mistakes flagged include seeking one perfect mentor, making big asks too early, and confusing mentorship with sponsorship. Use when users want career guidance, workplace advocates, professional network building, or advice from senior leaders.1.5kinstalls85Team RitualsThe team rituals skill Help users design effective team rituals. Use when someone is building team culture, creating recurring team practices, trying to improve team communication, or establishing operational rhythms for their organization. Documentation covers workflows, commands, and guardrails agents should follow when users invoke this capability. Key documented areas include **Understand the goal** - Ask what behavior or outcome they want the ritual to drive; **Apply the golden rituals framework** - Ensure rituals are named, templated, and known by every employee's first Friday; **Design for specificity** - Help create rituals that go beyond generic meetings to drive specific outcomes; **Plan for adoption** - Discuss how the ritual will be introduced and maintained over time. Use when developers or agents need structured guidance for team rituals tasks with evidence grounded in the bundled SKILL.md rather than generic advice.1.5kinstalls86Running OffsitesThe running offsites skill Help users plan and run effective team offsites. Use when someone is organizing a team retreat, planning a strategy offsite, trying to improve remote team cohesion, or preparing for quarterly planning sessions. Documentation covers workflows, commands, and guardrails agents should follow when users invoke this capability. Key documented areas include **Clarify the purpose** - Ask what outcome they want from the offsite (strategy, connection, planning); **Assess readiness** - Determine if there are underlying team issues that need addressing first; **Design the structure** - Help them balance work sessions with social connection; **Remove friction** - Guide them on logistics that make offsites productive. Use when developers or agents need structured guidance for running offsites tasks with evidence grounded in the bundled SKILL.md rather than generic advice. **Clarify the purpose** - Ask what outcome they want from the offsite (strategy, connection, planning) **Assess readiness** - Determine if there are underlying team issues that need addressing first **Design the structure** - Help them balance work sessions with social connection1.5kinstalls