refoundai/lenny-skills
85 skills124k installs87.5k starsGitHub
Install
npx skills add https://github.com/refoundai/lenny-skillsSkills in this repo
1Personal ProductivityPersonal Productivity is a journey-wide agent skill that helps solo builders and founder-operators manage time and tasks using distilled advice from two product leaders featured on Lenny’s Podcast. Invoke it when someone feels overwhelmed, struggles to focus, balances a day job with a product, or asks how to get more done without a formal productivity system. The skill first clarifies what is overwhelming and desired outcomes, then classifies whether the bottleneck is prioritization, focus, energy, or over-commitment, and finally applies practical patterns such as time boxing and written capture lists. It is lightweight research-backed coaching—not a project-management integration. Prism places its canonical shelf at Build PM because that is where roadmap and execution tradeoffs collide for indies, while journey-wide scope reflects use in Idea research sprints, Ship crunch, and Operate maintenance alike.5kinstalls2Competitive AnalysisCompetitive Analysis packages curated Lenny’s Podcast guest wisdom into an agent-ready playbook for solo and indie builders who need sharper market maps without hiring a strategy team. It walks you through assigned competitor ownership for a quarter, deep product immersion, SWOT work from the rival’s viewpoint, and a war-gaming day where small groups present findings—patterns operators like Annie Pearl describe for distributing research across the team. It also encodes April Dunford-style positioning discipline: identify what you must beat to win, enumerate competitive alternatives beyond direct logos, and treat status quo and DIY workflows as first-class opponents in B2B. Use it while you are still choosing a wedge, refining ICP, or preparing investor and sales narratives so messaging matches real buyer choices. The skill is editorial synthesis rather than a live data API, so you pair it with your own customer interviews, pricing experiments, and landing tests. Confidence is high for framework fidelity to the source insights; you still validate claims against your segment.2.2kinstalls3Brand StorytellingBrand Storytelling is a research-style agent skill that packages guest insights from Lenny’s Podcast into actionable narrative guidance for solo and indie builders who need positioning that scales beyond a one-off landing page. Instead of generic marketing advice, it surfaces how practitioners like Andy Raskin and April Dunford describe movements, rallying cries, and sales narratives you can test with real prospects. Use it when you have a rough product direction but weak differentiation, when sales and support tell different stories, or when you are preparing launch copy and investor or customer conversations. The skill does not run integrations or generate files automatically—it equips your agent with structured talking points and frameworks so you can draft positioning, refine pitch flow, and align messaging across validate, build, and launch work. It matters because inconsistent narrative is a common silent killer for small teams who cannot afford a full brand agency.2kinstalls4Writing PrdsWriting PRDs is a Lenny-skills agent skill that coaches solo builders and small teams through effective product requirements documents using principles from experienced product leaders. It fits the validate and build phases whenever you need to turn an idea into a spec engineering can execute: documenting product requirements, preparing specs, writing feature briefs, or defining scope before code. The workflow starts with problem and why-now context, defines how you will know the feature succeeded, chooses the right artifact (traditional doc, prototype, or executable evals), and pressure-tests whether the output drives action. Highlights include PR/FAQ-style customer clarity, leading with background and urgency, and balancing written specs with demos in an AI-assisted build workflow. Intermediate complexity; best when you have a direction but lack a shared, testable requirements narrative.2kinstalls5Content MarketingContent Marketing (Lenny Skills) is a research-style agent skill that distills dozens of Lenny’s Podcast guest takes into actionable content habits for solo builders. It is not a CMS integration or analytics dashboard; it is a structured insight library you invoke when planning distribution, overcoming posting friction, or choosing a thought-leadership posture. The material emphasizes consistency as a skill-building “vegetable,” long horizons punctuated by high-impact peaks, and authenticity tactics such as writing for an audience of one. With 23 guests and 35 tagged mentions, it gives quotable anchors and timestamps you can turn into calendars, positioning, or channel experiments. Use it while growing an audience after ship, or while launching when you need a credible content motion without hiring marketers.2kinstalls6Startup Ideationstartup-ideation is an agent skill that helps solo founders generate and pressure-test business concepts using curated frameworks from two product leaders featured in Lenny-style guest insights. It prompts you to map personal experience and skills, audit whether your information sources are differentiated, and apply a Why Now lens—what could be built today that was not viable yesterday because of technology or consumer shifts. The workflow balances divergent brainstorming with practical filters so you avoid crowded tarpits and chase opportunities that match your edge. It is most natural in the Idea phase but carries forward when you revisit scope in Validate or reconsider positioning before launch. The skill is conversational and methodology-driven rather than a code generator; outcomes are clearer hypotheses, sharper problem statements, and a short list of ideas worth a landing page or prototype test.2kinstalls7Vibe CodingVibe Coding is an agent skill grounded in Lenny’s Podcast insights that helps assistants guide users who build software through AI coding tools and conversational iteration. It targets solo founders, PMs, and designers who need a credible functional prototype—often in roughly half an hour—instead of a slide deck or static mock. The skill explains when to lean on AI generation, how to sequence prompts and feedback loops, and why treating vibe coding as a durable skill changes what “shipping a concept” means for non-engineers. Its primary home is Validate → prototype because the documented use cases are proofs of concept and resume-worthy builder fluency before a full Build phase commit; the same method extends into Build when you flesh out UI and agent-backed features. It is methodology, not a single integration: invoke it whenever someone is exploring AI-generated code without a traditional engineering background, then hand off to planning, review, or implementation skills once the prototype direction is clear.2kinstalls8Ai Product Strategyai-product-strategy is a research-oriented agent skill that distills Lenny’s Podcast guest wisdom into actionable AI product strategy guidance for solo and indie builders shipping algorithm-heavy or LLM-powered products. It is not an implementation generator; it supplies named insights, tactical bullets, and framing for decisions that product-minded builders face before and during build—such as which outcomes algorithms should optimize, which judgments must stay human, and how to leverage proprietary data as a moat. The skill fits builders who wear the PM hat and need citable, opinionated patterns instead of generic “add AI” advice. Use it when drafting scope, evaluating feature bets, or aligning growth metrics with editorial or expert quality. With 94 guests and 179 indexed mentions, it gives enough breadth to stress-test strategy memos and agent-generated roadmaps without pretending to replace customer discovery or legal review.1.8kinstalls9Giving PresentationsGiving Presentations is an agent skill that coaches solo builders and founders through narrative-first talks before slide tooling. It asks about audience, stakes, format, and time, then helps define a single arrow sentence—the only takeaway—and selects stories and data as the bow. Guidance draws on product-leader practices for contrast, state changes, and memorable structure, plus rehearsal and anxiety management for live delivery. Use it when preparing a deck, keynote, investor conversation, or any high-stakes room where engagement matters more than bullet density. It fits indie operators who must pitch, launch, and grow in public without a communications team. The skill keeps agents focused on remembrance and delivery quality rather than default template slides, which improves launch events, validation pitches, and recurring all-hands updates across the journey.1.7kinstalls10Systems ThinkingSystems Thinking is a journey-wide reference skill that packages Lenny’s Podcast guest wisdom for solo builders who must reason about products as ecosystems, not feature backlogs. It aggregates short, attributable quotes and insights from guests such as Hari Srinivasan, Melissa Perri and Denise Tilles, Seth Godin, and Sriram and Aarthi on topics like managing complex ecosystems, automating recurring pains, and mapping every player’s incentives. There is no installable CLI or checklist count—the value is procedural knowledge you invoke before committing to positioning, partnerships, pricing side effects, or internal workflows. Use it when an agent or you need language and mental models for “seeing the system,” anticipating downstream effects, and deciding where to build frameworks instead of one-off fixes. It complements validation and build planning skills by supplying strategic context rather than execution steps.1.7kinstalls11Founder SalesFounder Sales is a research-style agent skill that packages Lenny’s Podcast guest insights for solo and indie builders who sell their own product. It synthesizes 16 guests and 28 mentions into actionable patterns—especially that a large share of B2B deals die from the buyer’s inability to choose confidently, not from picking a competitor. You use it when you are writing outreach, running discovery calls, or refining a sales narrative and need credible framing instead of generic SaaS playbooks. The skill emphasizes acting as a guide, reducing decision stress, and avoiding FOMO tactics that backfire on overwhelmed prospects. It fits the Validate phase when you are proving willingness to pay, and remains useful in Grow when you refine lifecycle sales motion. It does not replace a CRM or outbound automation; it injects procedural knowledge your coding agent can cite while you draft emails, talk tracks, or positioning docs.1.7kinstalls12Positioning MessagingPositioning & Messaging distills Lenny’s Podcast corpus into agent-ready guidance for solo builders who must explain a product without a marketing team. The skill surfaces how guests like Adam Grenier advocate hyper-specific details and analogies so prospects grasp the exact curiosity or job you solve, and how Andy Raskin warns against the classic arrogant-doctor pitch of pain, solution, and superiority bragging. Agents can pull framed insights, tactical bullets, and timestamped quotes while you draft landing heroes, investor narratives, onboarding emails, or App Store subtitles. It is research procedural knowledge—not a copy generator—so output quality depends on applying patterns to your niche. Use early in Validate to lock scope and differentiation, then again in Launch when distribution channels need a coherent story. The compiled set spans dozens of voices, making it useful when you want plural expert lenses instead of one generic marketing template.1.6kinstalls13Setting Okrs GoalsSetting OKRs & Goals is a Lenny-skills reference pack that distills how experienced product leaders set objectives when simple one-number OKRs break down. Solo and indie builders use it when planning a quarter, aligning a tiny team, or running a marketplace-style product where consumer, supply, and ops metrics pull in opposite directions. The skill surfaces guest patterns such as breaking output goals into movable inputs—visits, conversion, reorder—and assigning unique ownership so teams do not collide on the same north star. It also documents when granular OKRs fail in multi-sided systems and when narrative big bets communicate holistic tradeoffs better than competing key results. Install it as procedural knowledge for your agent during roadmap and metric design sessions; it does not run code or connect to HR systems. Pair it with validation and growth planning when you need defensible goal structures before implementation plans or analytics instrumentation.1.6kinstalls14Behavioral Product DesignBehavioral Product Design is a Lenny-style agent skill that helps solo builders and small product teams translate behavioral science into concrete product decisions. Instead of generic UX advice, it walks through the action you want users to take, what blocks that behavior, and which psychological principles apply—loss aversion for streak retention, present bias for immediate rewards, status quo for defaults, and related nudges. It is useful when you are shaping onboarding, habit loops, friction reduction, or retention features and need interventions grounded in how people actually decide. The skill does not replace analytics or A/B infrastructure; it gives you a repeatable design conversation you can run before committing to specs or agent implementation plans.1.6kinstalls15Sales Qualificationsales-qualification is an agent skill that coaches solo founders and indie builders through lead qualification using product-leader patterns from the Lenny corpus. It starts by mapping how you currently decide who gets a second call, then sharpens disqualification criteria, discovery questions, and a lightweight framework so first conversations end in a firm yes or no. Use it when pipeline activity feels busy but closes stay flat, when you need a discovery script before outbound, or when validating whether a niche is worth sales effort during early pricing conversations. The skill is conversational and methodology-heavy rather than CRM integration—it complements Grow lifecycle and Validate pricing decisions without replacing a formal CRM.1.5kinstalls16Designing Growth LoopsDesigning Growth Loops is an agent skill that walks solo and indie builders through viral mechanics, referral programs, and product-led acquisition using frameworks distilled from experienced growth leaders. It starts by identifying whether you need a viral, paid, content, or product-led loop, then validates that unit economics and stickiness can support the mechanic before you invest engineering time. The workflow emphasizes finding the authentic moment users want to share—not bolt-on invite spam—and shaping the loop so each cycle reinjects demand. Guidance stresses dominating one primary loop before diversifying channels, treating viral growth as a learnable system rather than luck. Use it when you have a live or near-live product and need a coherent self-reinforcing growth engine instead of scattered experiments.1.5kinstalls17Technical RoadmapsTechnical Roadmaps is a Lenny-skills reference pack that gives solo builders and small eng leads quotable, tactical guidance on how to write technical strategy that teams can actually critique. Rather than generating a Gantt chart, it encodes guest insight from Will Larson: if strategy is not written down, you cannot tell whether a PM is ineffective or executing a misunderstood plan—documentation is the baseline for organizational debugging. The skill emphasizes Richard Rumelt’s structure (diagnosis, guiding policies, actions) and a deliberately boring but effective policy many companies underuse: constrain the org to the standard kit already in production so limited energy goes to customer problems, not new languages and providers. Install it when you are drafting a quarterly technical roadmap, pushing back on tool churn, or preparing eng leadership conversations where you need aligned vocabulary without rereading full podcast transcripts. It pairs well with planning skills that produce implementation plans after strategy is agreed.1.5kinstalls18User Onboardinguser-onboarding is a research-style agent skill that packages Lenny’s Podcast guest insights on in-product onboarding for solo SaaS and app builders. It is explicitly not new-hire onboarding: it focuses on the first-use path, aha moments, and why polished features can still stall adoption. The readme synthesizes quotes from Cam Adams on pre-launch onboarding pivots, Dan Hockenmaier on early-experience retention inflection, Grant Lee on making the first 30 seconds feel magical, and Merci Grace on designing from the tutorial like a game. Use it when you are shaping activation flows after validate, tightening launch-ready first miles, or diagnosing drop-off in grow. Agents can cite these patterns when writing specs, reviewing funnels, or comparing onboarding variants without pretending one guest playbook fits every vertical. Pair with your own analytics and experiments—the skill supplies principles and memorable heuristics, not a single funnel template.1.5kinstalls19Defining Product VisionDefining Product Vision is a research-oriented agent skill that packages Lenny Podcast guest wisdom into patterns solo founders can reuse when they articulate what they are building and why it matters. Rather than generating a vision from scratch in one shot, it orients you toward how experienced product leaders marry core value—journalism, infrastructure, or another sun product—with experiences that help people act on that value. Tactical excerpts cover portfolio thinking, brand heritage, trust, and how satellite offerings inherit DNA from a primary offering. Install it when you are early in a venture or repositioning an existing product and want citable language and metaphors before validation experiments or roadmap planning. It complements execution skills that write specs or plans; it does not replace customer interviews, metrics, or legal review of claims.1.5kinstalls20Prioritizing RoadmapPrioritizing Roadmap is a research-style agent skill that packages Lenny Rachitsky guest wisdom into actionable guidance for sequencing product and growth work. Solo and indie builders install it when they have too many ideas, conflicting inputs, or a backlog that does not clearly ladder to a growth model. The material stresses structured prioritization: labeling what you believe versus what you still need to learn, choosing the problems that move your model, and ordering experiments so each step informs the next. It is not a scoring calculator or Jira plugin—it is procedural knowledge you invoke while writing roadmaps, quarterly plans, or experiment backlogs. Use it in validate when narrowing scope, in build when ordering PM work, and in grow when sequencing growth bets. Highlights draw from operators who built at scale; you adapt the principles to one-person roadmaps and agent-assisted planning docs.1.5kinstalls21Design SystemsDesign Systems is a Lenny-skills-style agent guidance package that walks solo and indie builders through when and how to invest in a design system—not just a Figma file, but tokens, a component library, and documentation that non-designers can follow. It opens by assessing whether you need consistency, speed, or both, and whether you are at the right company stage for formalizing a system. From there it helps define scope across libraries, tokens, and docs, designs for adoption so engineers and PMs do not drift from brand, and plans evolution as the product grows. Core principles include separating conceptual block-frame logic from production-ready comps, treating the system as a lever for scaling output through agencies or contractors, and framing design systems as a reason customers upgrade tiers when you sell B2B. Use it when you are creating a component library, establishing tokens, scaling brand consistency across surfaces, or debating whether a full system is worth the overhead yet.1.5kinstalls22Problem DefinitionProblem Definition is a Lenny Skills knowledge pack that distills how world-class product leaders frame, test, and prioritize the problems worth solving. For solo builders who lack a PM bench, it turns podcast-grade pattern matching into agent-ready context: when metrics look fine but users stall, when compensation structures misalign with delivered value, and when the marginal user—not the power user—should drive the next fix. Install it during early discovery or when re-scoping a feature so your agent argues from named guest tactics instead of generic startup advice. It does not replace customer interviews; it sharpens the questions and prioritization heuristics you bring into validate and build.1.4kinstalls23Usability TestingUsability testing is a Lenny-skills agent package that walks solo builders through practical user validation without pretending you need a UX lab. Invoke it when you are validating a concept, hunting friction in a flow, or trying to understand why people bounce before you ship more code. The skill compresses product-leader patterns into a short playbook: clarify whether you are testing value, usability, or conversion; pick the right fidelity from fake doors and Wizard of Oz through live product tests; design scenarios and observation; and wire results into iteration. It argues you can fake the experience before building production automation and that small, representative samples surface sharp insights—useful for indie SaaS, mobile apps, and content products alike. It is methodology, not a recruiting panel or analytics MCP: you still run sessions and own synthesis. Best early when specs are still fluid; less necessary when you only need automated A/B infra without human sessions.1.4kinstalls24Writing Specs DesignsWriting Specs & Designs is a research-backed reference skill that distills Lenny’s Podcast guests into actionable product and design guidance for solo builders who must spec features without a full design org. It emphasizes fast alignment through rough whiteboard sketches that invite correction, ruthless efficiency on mobile flows where each tap can trigger a bounce, and intentional visual hierarchy before high-fidelity work. Use it when you are scoping a feature, writing a PRD, or arguing for simpler UX with evidence from experienced operators. It does not generate wireframes or code; it informs how you write specs and facilitate design conversations. Complexity is beginner-friendly—read and apply insights—but judgment is intermediate when translating quotes into your niche. Pairs naturally with implementation planning skills once the spec direction is stable.1.4kinstalls25Conducting User InterviewsConducting User Interviews is a research skill distilled from Lenny’s Podcast: dozens of operators explain when to leave the dashboard, how to observe real tasks, and how interviews expose conflicts between user mental models and product assumptions. It is aimed at solo founders who cannot afford a full UX lab but still need credible discovery before they prototype or price. The skill surfaces tactical advice—use analytics as a compass not a verdict, run contextual inquiry in users’ environments, and look for orthogonal blockers that cohort reports smooth over. It complements generic interview scripts by anchoring recommendations to named practitioners and concrete situations. Use it when you are defining who the product is for, debugging activation, or localizing features, then pair findings with validation artifacts like scoped PRDs or landing tests.1.4kinstalls26Written CommunicationWritten Communication is a journey-wide agent skill that packages Lenny’s Podcast guest wisdom for solo founders who lead through words more than headcount. It helps you notice when the same strategic story appears in ten separate one-on-ones and convert that into a short document teammates, users, or investors can consume without scheduling you. The compiled notes stress that leadership is communication—success means the artifact or verbalization actually changed how others think—and that silence and missing check-ins send signals too. Tactical threads include metaphor to invite engagement, multimodal formats when one channel stalls, and taking ownership of comprehension rather than blaming the audience. Use it whenever you are drafting a spec in validate, a launch note in grow, an incident summary in operate, or a roadmap narrative in build, not only for marketing copy. It is research-backed editorial guidance, not a template generator.1.4kinstalls27Enterprise SalesEnterprise Sales packages curated insights from Lenny’s Podcast guests into an agent-readable skill for solo and indie builders selling into organizations. It centers on how enterprise deals really close: buying committees of roughly five to seven people, a champion who must build internal consensus, and an economic buyer who signs the check. Rather than feature pitches alone, the skill emphasizes a unifying strategic narrative that gives sales conversations shared context across diverse stakeholders. You use it when you are moving upmarket, drafting enablement for a champion, or restructuring positioning for committee scrutiny. The content is reference-grade procedural knowledge—guest quotes, insights, and bullet tactical advice—not a CRM integration. It pairs well with pricing and positioning work earlier in the journey and with distribution narrative work at launch, but its canonical home is growing revenue through structured B2B lifecycle sales.1.4kinstalls28Pricing StrategyPricing Strategy is a Lenny-skills advisory agent skill that walks solo builders and indie founders through monetization design using principles from dozens of experienced product leaders. Install it when you are choosing prices for the first time, debating freemium versus paid, stress-testing willingness to pay, or migrating between pricing models after launch. The workflow starts by clarifying your business model and customer segments, then ties price to delivered value, surfaces competitive and technical constraints, and helps you design tiers you can revise as you learn. It emphasizes WTP discovery early, treats price as a measure of perceived value rather than a cost-plus afterthought, and pushes continuous revisiting instead of one-off guesses. It fits Prism’s Validate journey hub for pricing decisions and remains useful in Grow when you refine packaging and revenue.1.4kinstalls29Retention EngagementRetention & Engagement is a Lenny-skills research pack for solo builders running consumer apps, games, or subscription products where repeat sessions matter more than a single checkout. It compresses dozens of operator anecdotes into actionable patterns: treat retention as gold before leaning on day-one monetization, redesign failure moments to highlight brilliant moves instead of blunders, and sanity-check whether your D1 retention sits in a healthy band for your category. The skill is consultative—it helps you audit loops, interpret benchmarks mentioned by guests, and prioritize experiments that compound engagement rather than one-off campaigns. It does not replace your analytics warehouse or push-notification stack; it supplies product judgment for lifecycle changes that affect return rate, review volume, and subscription conversion after habit is established.1.4kinstalls30Analyzing User FeedbackAnalyzing User Feedback is a Lenny-skills research package that gives solo builders a dense, citable playbook distilled from dozens of operator interviews. Instead of generic advice to “talk to users,” it encodes where high-signal pain shows up (for example unfiltered Reddit threads), how to avoid drowning in telemetry (use production monitoring to flag traces worth human review), and how to translate bursts of complaints into failure patterns you can ship against. For a one-person team, that matters because you cannot manually read every support ticket and LLM trace— you need heuristics for what to open first. The skill is reference-heavy: named guests, direct quotes, and tactical bullets your agent can pull into prioritization memos, experiment backlogs, or weekly growth reviews. It spans Validate when you are still proving fit, Grow when scaling feedback loops, and Operate when production behavior contradicts what interviews suggested.1.4kinstalls31Career TransitionsCareer Transitions is a journey-wide research skill that packages Lenny Rachitsky podcast guest wisdom into an agent-queryable brief on pivots, employer selection, and long-term skill strategy. Solo builders use it whenever a path decision is on the table—not only at first hire—because the insights cover exploration modes, when to exploit depth, how to evaluate managers and companies, and how to navigate intentional career moves without treating every job as identical. The skill does not write your résumé or run outreach; it supplies cited opinions and playbooks you combine with your constraints. It is especially useful before joining a startup to ship your own product later, or when choosing whether to stay employed while validating an indie idea. Expect a reading and synthesis workflow grounded in named guests and recurring themes across many episodes.1.4kinstalls32Launch MarketingLaunch-marketing is a research-oriented agent skill that distills launch and awareness guidance from Lenny’s Podcast guests into quotable insights and actionable checklists. Solo founders use it when they are past build and need distribution ideas grounded in how successful operators actually got attention—organic social demos, single-outlet exclusives, and storytelling that ties funding to customer momentum rather than vanity announcements. The material spans multiple moments in the journey but shelves under Launch distribution as the primary entry when you are planning a release. Complexity is beginner-friendly: it is reading and applying tactics, not configuring infra. Pair it with your own positioning doc and analytics after traffic arrives. The skill does not replace a full PR firm; it gives an indie builder a vetted pattern library before spending on ads or blasting embargoes to every outlet.1.4kinstalls33Measuring Product Market FitMeasuring Product-Market Fit is a research-oriented Lenny-skills pack that aggregates podcast guest insights so solo builders can judge whether real fit exists—not just excitement or a large TAM slide. It belongs primarily in validate when you are scoping an offer, interpreting early traction, or deciding to pivot after market change; it also supports grow and idea phases when you reassess retention, positioning, or economic shifts. The content emphasizes that PMF is not permanent, that macro changes can zero out prior fit, and that conflating addressable market size with demonstrated demand is a top failure mode. Use it with an agent to stress-test your metrics narrative, align definitions across audience and product, and pull quoted tactical advice from named guests. Intermediate complexity; strongest when you already have some customer signal and need structured skepticism.1.4kinstalls34Community BuildingCommunity Building is a Lenny-skills research pack that helps solo builders and small teams foster communities that actually move the business—not vanity Discord counts. Canonical placement is grow lifecycle: retention, advocacy, and member-led distribution; it also informs validate when you test a narrow community wedge and launch when word-of-mouth is your channel. Insights cover starting with a small highly engaged core, setting explicit collaboration norms, facilitating with positive reinforcement, and using community pull to build brand recognition that can support upmarket expansion. The skill is reference-heavy—guest quotes and tactical bullets for agents to apply to your niche, whether developer tools, Notion-style templates, or creator-led products. Intermediate complexity; best when you have a fledgling audience and need operating principles for norms, scale, and engagement quality.1.4kinstalls35Designing SurveysDesigning Surveys is an agent skill that walks solo and indie builders through customer research instruments using practices from nine product leaders. It fits whenever you need satisfaction signal, problem discovery, or feature priority—not only at first launch. The workflow starts by clarifying whether you are measuring satisfaction, surfacing problems, or ranking opportunities, then selects the right instrument among CSAT, PMF-style probes, or tailored questions rather than copying generic NPS widgets. Core guidance pushes CSAT with well-scaled items when satisfaction is the goal, and Nicole Forsgren–style constraints that limit respondents to three priorities followed by frequency, which keeps ranking data actionable for a one-person product team. You also get help writing questions that measure a single construct and reaching people with recent, relevant product experience so answers are not stale advocacy. Use it in validation before committing roadmap, when tuning onboarding or pricing narratives, and in growth when you need lifecycle feedback without polluting analytics with muddy scales.1.4kinstalls36Design EngineeringDesign Engineering is a Lenny-skills advisory agent skill that helps solo builders and small teams understand an emerging role combining design taste with production-ready code. Product leaders at Snap, Captions, and Vercel describe design engineering as a function that collapses slow design-to-engineering handoffs so prototypes become shippable UI sooner. Use it when you are creating a design engineering function, writing a job description, deciding whether to hire a hybrid profile, or aligning a two-person indie stack where one person wears both hats. The skill does not replace a component library or Figma-to-code tooling; it supplies role definition, organizational patterns, and narrative from practitioners. Complexity is beginner-friendly for founders learning the concept and intermediate for leads structuring a team. It pairs naturally with Validate scoping conversations and Build-phase frontend execution. Invoke when the gap between mockups and merged PRs is your bottleneck, not when you only need a one-off CSS tweak.1.4kinstalls37Building With LlmsBuilding with LLMs aggregates actionable quotes and tactical notes from dozens of Lenny’s Podcast guests into a single agent skill for builders working on AI-native products. Solo developers use it when they need credible patterns—natural language to SQL in Slack, fast AI prototypes of core screens, or architectural ideas like compaction when context windows limit long agent sessions—without rereading hundreds of episodes. It does not replace your stack-specific integration skills; it informs what to build and why. Placement on Build / agent-tooling reflects implementation-heavy content, while validate and idea scenarios still apply when you are choosing explore tools or scoping an LLM wedge. Pair it with concrete builder skills in your repo when you move from insight to wiring Pyodide, MCP, or production inference.1.4kinstalls38Product Led SalesProduct-Led Sales is an agent skill that helps solo founders and small SaaS teams add a sales-assisted layer on top of an existing product-led growth motion without abandoning self-serve. It distills frameworks from two Lenny’s Podcast guests: Elena Verna’s view that product-led sales converts usage generated via self-serve into larger contracts with a salesperson attached, and Hila Qu’s description of funnels where sales receives product signals and reaches out with contextual help. The skill walks you through understanding current PLG and sales infrastructure, defining trigger criteria such as product-qualified leads or accounts, and building handoff processes so outreach feels helpful rather than cold. It is aimed at the transition from pure PLG to hybrid models—metrics like PQAs, organizational ownership questions, and when a human should join the deal. Use it when expansion revenue depends on behavior inside the product, not only marketing top-of-funnel, and you need a structured conversation with your agent about criteria, sequencing, and accountability before hiring or reorienting a part-time sales effort.1.4kinstalls39Stakeholder AlignmentStakeholder Alignment is a reference agent skill that distills how experienced operators align product, growth, design, and leadership when incentives diverge. Solo builders wear every hat, so a feature push, growth experiment, or launch deadline often triggers silent resistance from collaborators—or from future-you if quality debt stacks up. Rather than a rigid template, the skill surfaces curated guest insights: communicate experiments as part of a strategic bet, learn what each stakeholder optimizes for, and temporarily set aside your goals to understand theirs before re-anchoring on shared outcomes. It fits whenever you need language and mental models for buy-in, not when you need wireframes or code. Canonical placement is Build PM because alignment work clusters around roadmap and delivery, but the same patterns apply when validating scope with advisors, shipping cross-team launches, or growing through lifecycle programs that touch support and marketing.1.4kinstalls40Ai EvalsAI Evals is an agent skill for solo builders shipping LLM-powered features who need evals to be as deliberate as product requirements—not an afterthought once users complain. It helps you clarify what feature or model behavior you are testing, define “good” in observable terms, and choose rubrics, test cases, and measurement methods aligned with insights from AI practitioners (including themes from Lenny’s podcast guests on error analysis and benchmark design). The workflow treats evaluation as its own discipline: separate from classic QA, separate from vague “make the AI smarter” prompts, and essential when model output is the user-facing product. Use it while scoping an agent tool, before a major prompt or retrieval change, or when you need a repeatable scorecard for regression checks. Implementation guidance stays practical—enough structure to start a small eval set and iterate—without replacing your production observability stack.1.4kinstalls41Planning Under UncertaintyPlanning-under-uncertainty is a research-style agent skill that compiles Lenny Podcast guest wisdom for product leaders facing ambiguous markets, platform crises, and problems with no existing playbook. Solo builders and indie PMs install it when they need reframing—prioritize diagnosis over panic, build solutions rather than merely forecasting failure, and develop grit for unprecedented constraints—before locking scope or burn rate. The corpus spans dozens of guests with quotable insights and tactical bullets, making it useful as conversational context for agents helping with strategy memos, pivot decisions, or stakeholder updates. It does not generate code or tasks; it supplies judgment patterns you apply in idea research, validation tradeoffs, build prioritization, and operational firefighting. Treat it as editorial PM knowledge to pair with your own data and timelines.1.3kinstalls42Conducting InterviewsConducting Interviews packages curated wisdom from Lenny's Podcast into an agent skill solo builders use when they need better conversations—not slide decks. Whether you are doing discovery with early users, pricing interviews, or your first hire, the skill surfaces concrete tactics: excavate implicit success criteria into rubrics, ask about product failures to test honesty and learning, and probe how people prepared for the conversation. It is research and methodology content rather than a CRM or scheduling integration, so you bring the calendar and notes; the skill helps you design the script and evaluate answers consistently. Indie founders who otherwise copy generic question lists get guest-attributed insights and timestamped sources to adapt. Use it when validation feels fuzzy, hiring feels subjective, or you want structured interviews that compound across Idea research and Validate scope work without hiring a coach.1.3kinstalls43Product OperationsProduct-operations is a research-oriented agent skill packaging curated quotes and insights from five Lenny’s Podcast guests—Brian Tolkin, Christine Itwaru, Geoff Charles, Melissa Perri, and Denise Tilles—into one reference for how product operations functions actually emerge in fast-moving companies. Solo and indie builders who act as their own PM can use it to decide when to invest in lightweight ops rituals: release cadence, sales-to-product feedback loops, and operational tasks that otherwise steal focus from roadmap work. The skill emphasizes that product ops creates enabling systems and does not remove PM decision rights. It is ideal when you are scaling from founder-led shipping to a small team and feel constant friction between building features and keeping launches orderly. It is not a terraform of Jira macros or a substitute for hands-on customer discovery in the Idea phase.1.3kinstalls44Product Taste IntuitionProduct Taste & Intuition is a journey-wide coaching skill that helps solo builders strengthen how they evaluate UX, positioning, and scope when metrics are thin. Instead of a checklist tool, it guides the agent to ask what products you study, where judgment feels weak, and which deliberate practice will close the gap. Core ideas include treating intuition as fast hypothesis generation to validate later, and elevating taste as the moat when AI makes shipping cheap. The skill is ideal in Claude Code or Cursor when you are stuck between options, reviewing a competitor landing page, or deciding whether a feature feels premium or slop. It does not replace analytics; it pairs with validation work once hypotheses exist. Use whenever product decisions need qualitative bar-setting across the solo journey.1.3kinstalls45Running Decision Processesrunning-decision-processes distills how experienced operators make high-stakes calls without defaulting to generic advice. It packages guest-tested tactics such as Ada Chen Rekhi’s Curiosity Loop—email a small trusted panel with a constrained choice set so busy people return rationale, not noise—and values-based “play the movie forward” checks against a personal top three to five stack-rank. Solo builders can apply the same moves when picking a niche, a podcast angle, a hire, or a feature bet: curate who you ask, make the ask cheap, solicit why answers rank, and close the loop. The skill is editorial research, not a ClickUp integration; your agent uses it to facilitate decision memos, interview guides, and pre-mortems whenever uncertainty is high and commitment is expensive.1.3kinstalls46Writing North Star MetricsWriting North Star Metrics is a Lenny-skills knowledge pack that helps solo founders and small teams articulate one organizing success metric without drowning in dashboard vanity. Pulled from twenty-seven guests and thirty-five mentions, it stresses that the power of a north star is communication and alignment—not spreadsheet perfection. Early-stage readers get explicit guardrails: CTR and retention can mislead at tiny cohorts, so you favor magic moments and qualitative pull until the product earns quantitative rigor. Later passages push memorable, discrete targets leaders can repeat (“ten friends in fourteen days”) so execution replaces academic metric wars. Use it when scoping a new product, reframing growth goals, or preparing investor and team narratives. The skill delivers research-backed bullets and quotes agents can turn into metric definitions, OKR drafts, and roadmap guardrails rather than automated analytics.1.3kinstalls47Startup PivotingStartup Pivoting is an agent skill that walks solo and indie founders through when and how to change direction using frameworks from experienced product leaders. It is for builders who question their current path, see poor traction, feel stuck before product-market fit, or consider a major strategy change—not for polishing a working growth engine. The skill starts by assessing traction, time on the problem, and what you have learned; then it checks whether you have truly exhausted possibilities or only one narrow version of the idea. It challenges pivot magnitude (many teams need a 200% pivot, not a 10% tweak) and applies the Four Ps across problem, persona, product, and positioning. Use it in validate when scope and fit are unclear, and in idea when early research suggests the wedge may be wrong. Plain conversation output; no code or infra required.1.3kinstalls48Fundraisingfundraising is an agent skill that helps solo founders and small teams navigate capital strategy using condensed insights from Lenny’s Podcast guests. It is built for moments when you are tempted to raise because that is the default playbook, but have not yet aligned funding with product goals, runway needs, and appetite for the venture treadmill. The skill walks through questioning the raise assumption, clarifying stage, and only then applying tactical advice such as leading with your strongest proof on slide one and enduring the long sequence of investor conversations. It is advisory rather than a filing or CRM integration, so your agent acts as a structured coach drawing on attributed guest quotes and themes. Install it when you are drafting or refactoring a pitch deck, preparing for first meetings, or debating bootstrap versus VC—not when you need legal term-sheet execution or cap-table software.1.3kinstalls49Platform StrategyPlatform Strategy is an agent skill that helps solo and indie builders design and execute platform businesses—marketplaces, API platforms, ecosystems, and developer platforms—using distilled frameworks from product leaders cited in the skill. It walks you through clarifying platform type, identifying network effects across sides, assessing lifecycle stage, and designing trust and governance so chicken-and-egg and policy mistakes surface before code. Unlike a generic business canvas chat, it encodes operator quotes and repeatable steps for when someone is deciding API strategy, thinking about multi-sided network effects, or standing up an internal developer platform. Use it during validation and early build when scope still moves; pair it with pricing and distribution planning as you move toward launch. The skill is editorial and strategic—no install counts or store metrics—so outcomes are clearer specs and decision records your agent can turn into roadmaps.1.3kinstalls50Evaluating Trade OffsEvaluating Trade-offs is a Lenny-skills reference package that distills how experienced product leaders decide under uncertainty. It is not a shell script or API wrapper; it is procedural knowledge you invoke when a solo builder must choose between directions, experiments, or shipping cadences without drowning in spreadsheet precision. The material pushes order-of-magnitude comparisons when forecasts are fuzzy, and argues for rigorous thought experiments so obvious failures never reach the backlog. That makes it journey-wide: the same mental models help at idea filtering, validate scoping, build sequencing, ship cut lines, launch bets, and operate prioritization. Use it as an editorial guardrail before committing agent time to implementation plans or A/B scaffolding that the narrative already predicts will fail.1.3kinstalls51Running Design ReviewsRunning Design Reviews is an agent skill that packages how strong product teams run critique before UI hits production. Indie builders often skip formal review because they are the only designer—then edge cases and unclear tradeoffs slip into App Store screenshots, onboarding, or checkout flows. The skill pulls Lenny guest patterns: ask for specific feedback types, surface risks you are already accepting, and reserve full leadership attention for large roadmap bets instead of every tweak. It also references extreme quality bars, such as founders reviewing every customer-facing screen, as a north star rather than a mandate for every team size. Use it when you are about to ship meaningful UI, not when you are still sketching early concepts. It complements agent code review skills by focusing on product semantics, flow coherence, and happiness across nuanced states—not lint rules.1.3kinstalls52Platform InfrastructurePlatform Infrastructure packages distilled podcast wisdom for solo and indie builders who are choosing what to build versus what to harden underneath. Instead of a checklist or automation, it surfaces how successful teams treat reliability, speed, encryption, and data residency as the product—not the feature list. You use it when you are debating microservices versus a monolith, planning a multi-tenant SaaS, or wondering why WhatsApp-scale products feel “simple” on the surface. The tactical threads push you to standardize exports, filters, and cross-cutting concerns once, then let feature work focus on unique logic. It pairs well with early architecture conversations and later operate-phase retrospectives when incidents expose weak foundations. It does not install tooling or scan your repo; it is editorial research meant to inform CONTEXT.md, ADRs, and prioritization discussions with your coding agent.1.3kinstalls53Cross Functional CollaborationCross-functional Collaboration packages guest insights from Lenny’s Podcast into an agent skill you invoke when planning how PM, engineering, design, data, and domain experts work as one mission. Solo and indie builders often skip explicit collaboration design and then fight rework when editorial judgment, metrics, and craft pull in different directions; this skill surfaces proven patterns—embedding editors on journalism-adjacent products, valuing expert judgment alongside KPIs, and letting design prototypes graduate into engineering PRs. It is curated procedural knowledge, not a CLI or MCP integration. Use it during ideation, validation scoping, build planning, launch coordination, and post-launch iteration whenever you are defining who sits on the mission and how decisions get made. The SKILL content is quote-backed with timestamps so your agent can cite specific guest framing in specs, retros, or stakeholder memos.1.3kinstalls54Evaluating CandidatesEvaluating Candidates is an agent skill that packages curated hiring insights from Lenny’s guest corpus into actionable evaluation heuristics for solo founders and small teams who cannot afford dedicated recruiting ops. It emphasizes building a balanced competency portfolio across the team rather than chasing one candidate who maxes every dimension, and it surfaces when internal transitions beat external searches because customer and execution knowledge already exist. Use it when you are defining a role, interviewing, or calibrating offer decisions against real product-leader advice instead of generic HR checklists. The skill is editorial synthesis—not an ATS integration—so the agent applies the principles in conversation while you keep your own scorecards and legal process. It matters for AEO-ready planning because it names concrete patterns (gap-first hiring, balanced teams, internal mobility) that builders cite when searching how experienced operators evaluate people.1.3kinstalls55Building Sales TeamBuilding Sales Team is an agent skill that packages Lenny’s Podcast guest wisdom into actionable guidance for founders adding sales to a product-led business. It is aimed at solo and indie builders who are moving past founder-led sales and need to avoid classic mismatches—such as hiring Oracle-style hunters when buyers are RevOps leaders on an inbound motion. The skill emphasizes matching rep profiles to how customers actually arrive today, whether inbound, outbound, or a blend, and designing journeys where self-serve and sales-assisted paths connect instead of competing silos. Use it when you are planning first sales hires, revisiting GTM after PLG traction, or debating when to add a sales-assist layer. It is editorial reference material, not a CRM integration; your agent synthesizes the insights against your stage, ACV, and buyer persona.1.3kinstalls56Coaching PmsCoaching-pms is a Lenny-skills agent package that helps you develop product managers using curated guest frameworks rather than generic management advice. Solo founders who have hired their first PM—or lead a tiny product trio—use it when running performance conversations, drafting development plans, or trying to level up team judgment. The skill anchors on operational rituals: agree what “good” looks like in your company, assess individuals against that bar, align on a shared growth vision, then document plans and follow up. It weaves in Bloom’s Taxonomy for skill diagnosis and emphasizes coaching as the main way product leaders at top companies scale impact. It does not replace hands-on product discovery for your own indie project when you are the only builder; it shines when people management and PM craft need structured coaching language.1.3kinstalls57Post Mortems RetrospectivesPost-mortems & Retrospectives is a Lenny-skills knowledge pack that distills how experienced product leaders run pre-mortems, post-mortems, and learning reviews. Solo and indie builders use it when they need objective exit criteria before a bet gets expensive, and when they want retrospectives that capture data, experiments, and user research instead of blame. The material emphasizes kill criteria—signals you agree upfront will trigger pivot or shutdown—because teams launch slowly and quit even slower once a project is live. It also references continuous documentation of impact and learnings at the team level. It is editorial procedural knowledge for agents, not an integration; pair it with your own planning and shipping rituals rather than expecting automated exports.1.3kinstalls58Working Backwardsworking-backwards is a journey-wide agent skill that distills Lenny’s Podcast guest insights into a repeatable product-planning ritual for solo founders who must choose what to build without a large PM org. It frames working backwards as aligning organizational and go-to-market machinery toward a concrete launch date while defining what must exist for the product to succeed—not merely drafting marketing copy. Guests emphasize starting from the customer and reasoning backward to engineering and business tradeoffs, using PRFAQ-style artifacts to surface compliance, legal, marketplace, and internal stakeholder risks early. Tactical advice includes writing multiple fully thought-through press releases to compare strategic routes and embedding mandatory FAQs for functions that can block shipping. Use it whenever you face an ambiguous bet, a new product line, or a leadership decision that needs a shared narrative before implementation plans. The skill is research and methodology content, not an automated deploy or code generator.1.3kinstalls59Organizational DesignOrganizational Design is a Lenny-skills research skill that helps solo founders and small-team leads think clearly about how to group people and ownership before a reorg hardens politics and slows shipping. It draws on condensed guest insights—Brian Chesky on returning to a functional, flatter startup model, and Gustav Söderström on the Apple–Amazon spectrum of central coordination versus parallel squads. The skill is conversational: it asks about your current structure, stage, and the problem you are solving, then maps trade-offs between speed, UX coherence, and dependency risk. It is not an HRIS or headcount planner; it is judgment support for product-led builders who are hiring their first PM, splitting frontend from backend, or undoing accidental silos. Use it when structure—not roadmap—is the bottleneck.1.3kinstalls60Managing TimelinesManaging Timelines packages product-leadership advice from Lenny’s Podcast into an agent-ready reference for indie PMs. Guests describe how to avoid over-promising far-future ship dates, how to separate discovery commitments from engineering delivery estimates, and how individual contributors can protect momentum with small daily rituals. For a solo builder, the skill helps you narrate realistic timelines to stakeholders—or to yourself—while you still run discovery, coding, and launch. It does not generate Gantt charts; it encodes judgment calls that reduce thrash: promise what is inside your control, finish solutioning before you fix a launch month, and start the hardest task with five minutes of focused effort. Reach for it when scoping milestones, updating a roadmap, or recovering from schedule slip.1.3kinstalls61Writing Job DescriptionsWriting Job Descriptions is a Lenny-skills agent workflow that helps solo and indie builders craft postings people actually respond to. Instead of copying generic responsibility bullets, you define what champagne-worthy success looks like twelve months after day one, name the non-negotiable spikes for the role, and describe the progress the hire will make—not chores you want to offload. The skill walks through candidate signaling (who feels invited vs. filtered out) using guest insights from Jonathan Lowenhar, Bob Moesta, and others packaged for agent-assisted drafting. Use it when you are opening your first role, reframing a contractor vs. employee hire, or rewriting a post that keeps attracting the wrong profile. It is editorial methodology, not an ATS integration: you still paste into LinkedIn, Ashby, or Notion—but the structure matches how strong product orgs hire.1.3kinstalls62Energy ManagementEnergy-management is a journey-wide agent skill that packages distilled advice from multiple Lenny’s Podcast guests into actionable frames for solo builders who cannot outsource every hat they wear. Instead of generic time-management tips, it focuses on energy drivers and drains, auditing how calendar blocks actually feel, and deliberately spending more time in zone-of-genius work while delegating or deleting energy-zapping tasks. Guests tie abundant mindset, role design, and superpower alignment to sustainable performance—relevant when you are researching markets, scoping MVPs, building features, shipping launches, or operating production incidents. Use it whenever calendar creep, burnout, or unclear prioritization threatens momentum, not only at quarter planning. The skill is research-shaped curated insight rather than a checklist integration, so your agent synthesizes scenarios and next steps from named frameworks rather than running shell commands.1.3kinstalls63Managing Tech DebtManaging Tech Debt is a Lenny-skills compilation that translates podcast guest experience into decisions solo builders face when shortcuts stop working. Use it when pricing engines, growth stacks, or internal tools cannot adapt to how you actually run the business— and when emotions make rebuild conversations hard. Each entry bundles a quote, insight, tactical bullets, and timestamps so your agent can argue from real operator stories rather than generic “refactor sometimes” advice. The themes include admitting when incremental fixes cannot deliver marketplace or ops control, and architecting today’s minimum viable systems without foreclosing needs a year or two out. It complements coding agents and review skills; it does not scan your repo or produce a debt register. After aligning on strategy, pair with implementation planning, security review, or infra skills for execution.1.3kinstalls64Scoping CuttingScoping & Cutting is a Lenny-skills digest that compresses guest advice on what to ship first and what to defer. Solo founders use it when scope creep, perfect-roadmap debates, or MVP minimalism threaten to launch something users do not care about. The skill surfaces quoted insights with timestamps, short interpretations, and bullet tactical advice—covering emotional resonance (lovable versus merely viable), fake-door and manual backends, and time-boxed decision traps. It does not replace your own customer interviews or metrics, but gives phrasing and patterns you can paste into planning chats with your coding agent. Reach for it when you are validating a subscription idea, trimming a v1 feature list, or choosing manual validation over a sprint of automation. After scope is locked, hand off to implementation planning or prototype skills rather than treating this file as a build spec.1.3kinstalls65Shipping ProductsShipping Products is a reference skill that distills how experienced operators actually ship: thoughtful tech integration after acquisitions, validation before loud launches, and aggressive but disciplined release timelines. Solo and indie builders use it when they are about to cut scope, announce a feature, or merge an acquired codebase and want precedent-backed guardrails instead of vibes. The material is organized by guest with quotes, insights, and short tactical lists, so an agent can cite a specific stance during planning or launch prep. It does not replace your own metrics or security review; it complements validate-and-ship work by surfacing how others avoided breaking trust, wasted PR, or irreversible public commitments. Best used while writing launch checklists, post-acquisition migration plans, or “should we announce yet?” decisions across validate, ship, and launch phases.1.3kinstalls66Having Difficult Conversationshaving-difficult-conversations is a journey-wide agent skill that distills Lenny’s Podcast guest insights into actionable language for feedback, radical candor, and sensitive management moments. Solo and indie builders wear every hat—founder, PM, and accidental manager—so delaying hard talks with a contractor, co-founder, or first hire can stall velocity as much as a bad deploy. The skill compiles dozens of guest perspectives on why managers avoid appearance or presence feedback, how to frame candor as kindness, and how to tie observations to impact the recipient can control. Use it before performance reviews, scope fights, pricing pushback, or partnership resets, not only when you formally “manage” people. It is research-backed procedural knowledge rather than a script generator: you still judgment-call tone and timing. It pairs well with promotion and planning skills when conversations follow documented expectations. Confidence is high for editorial breadth (43 guests) but you should adapt examples to your team size and legal context.1.3kinstalls67Evaluating New Technologyevaluating-new-technology is a research-backed agent skill that distills Lenny’s Podcast guest wisdom into practical filters for adopting new stacks—especially AI products pitched as instant wins. Solo and indie builders use it whenever they must decide whether a shiny SDK, agent platform, or automation vendor deserves a prototype slot, a paid pilot, or a hard pass. The material emphasizes updating stale assumptions as models improve, doubting magic “one click” deployments when data and infra are messy, and favoring partners that commit to pipelines that learn over time. It does not replace hands-on spikes or security review; it gives your agent a shared vocabulary for scope conversations in Validate and for re-evaluating tools again in Build, Ship, and Operate when the landscape shifts. Install it when you want defensible, citeable product judgment rather than generic hype checks.1.3kinstalls68Building A Promotion Casebuilding-a-promotion-case is an agent skill that aggregates Lenny’s Podcast guest advice into a practical promotion narrative for individual contributors and new managers on small teams. Indie builders often negotiate title and scope with a single founder-CEO, so the skill stresses demonstrating next-level scope before the ask and tying evidence to outcomes the company cares about—not a laundry list of manager preferences. Guests emphasize practicing leadership work early, using trial roles to test management, and avoiding promotion chasing that narrows impact to local approvals. Use it when you are six to twelve weeks from a review cycle, when you are stepping from IC to lead, or when you need to translate side-project wins into leveling language. It complements difficult-conversation skills for the actual meeting. It is editorial research, not a compensation calculator; you still need your company’s rubric and market data.1.3kinstalls69Running Effective MeetingsRunning Effective Meetings is a research-style agent skill that distills Lenny’s Podcast guest wisdom into facilitator-ready habits for people who run lean teams or wear every hat. It is not a calendar integration; it is procedural knowledge you invoke whenever a sync risks becoming a re-meeting factory. The corpus highlights Alisa Cohn’s three closing questions and Annie Duke’s framing that meetings exist for discussion, while discovery and decision-making should largely happen asynchronously beforehand. Solo builders use it with cofounders, contractors, investors, and early customers to end calls with explicit decisions, named owners, deadlines, and stakeholder loops. Highlights include sampling alignment in large groups, assigning a meeting czar for follow-through, and blocking the final minutes for verbal or on-screen confirmation. Journey-wide scope reflects that the same discipline helps validate scope conversations, ship-week standups, launch war rooms, and grow-phase retros—anywhere misalignment is expensive.1.3kinstalls70Delegating WorkDelegating Work packages research-backed leadership insights from Lenny's Podcast into an agent skill solo founders can use when they start handing off roadmap, ops, or implementation—whether to a first contractor, a co-founder, or a fleet of coding agents. Instead of generic management theory, it surfaces repeatable patterns: Ben Horowitz on managerial leverage (your report should push the org forward), Boz on refusing to rule when struggles are the right ones, and dozens of adjacent guest takes indexed for search inside the skill. For a one-person shop, the same ideas translate to agent workflows: define ownership, stop re-deciding every task, and evaluate whether your 'reports' arrive with proposals or empty queues. The skill is prose and quote-driven rather than a checklist integration; invoke it when you feel pulled back into every decision during Validate scoping, Build execution, Launch coordination, or Operate firefighting.1.3kinstalls71Building Team CultureBuilding Team Culture is a research-style agent skill that compiles Lenny’s Podcast guest wisdom into themed insights and tactical advice for founders and small teams. It is aimed at solo builders who are about to hire, partnering with a co-founder, or scaling past a one-person shop and need concrete norms—not generic HR slogans. Use it when you want evidence-backed patterns on decision rights, constructive conflict, psychological safety, and diversity as a product advantage. The material spans high-stakes partnerships, feedback culture, and recruiting teams that reflect your users. It does not install tooling or write code; it gives you language and rituals to adopt in offsites, hiring plans, and weekly operating rhythms so execution stays fast as headcount grows.1.3kinstalls72Negotiating OffersNegotiating Offers packages Lenny’s Podcast insights so builders can run calmer, clearer comp discussions—whether you are closing your first engineer, converting yourself to contract at a day job to fund nights-and-weekends, or explaining why your startup pays fairly but optimizes for learning. The skill steers you to diagnose what the other side is actually optimizing for, articulate explicit trade-offs instead of opaque ranges, and use structured proposals (like part-time contract continuations) that many employers accept but candidates never ask for. It is negotiation coaching distilled from Bob Moesta and Paul Millerd—not legal advice, cap tables, or benchmark spreadsheets. Pair it with a written role definition so “experience value” in the offer matches the job’s progress story.1.3kinstalls73Organizational TransformationOrganizational Transformation is an agent skill that coaches users through real organizational change toward modern product practices—moving from feature teams to empowered product teams, modernizing legacy processes, and shifting culture in how product is built. It draws on curated guest insights from John Cutler and Marty Cagan, including the warning that many companies treat framework adoption as the destination rather than a means, and that transformation requires techniques beyond team restructuring alone. The skill asks you to clarify your starting point, then applies those leader perspectives to nudge change without systemic rejection. It is best for solo founders, product leads, and small teams who are redesigning how they ship—not for pure implementation tasks like wiring auth or writing HTML. Use it when you are planning operating-model change across validation, build, and ongoing iteration rather than looking for a single integration checklist.1.3kinstalls74Managing UpManaging Up is a reference agent skill that packages distilled advice from Lenny’s Podcast guests on how ICs and leads navigate bosses, CEOs, and organizational dysfunction without torpedoing their own credibility. Solo builders still hit this when they freelance for enterprises, report to a founder-investor, or sell into teams where one executive owns the narrative. The readme compiles named guests, pull quotes, labeled insights, and bullet tactical advice—for example acknowledging ‘organizational kayfabe,’ introducing disconfirming evidence carefully, or writing parallel hot-take documents during onboarding. It is not a deployment or coding workflow; it is procedural knowledge your agent can cite when you draft updates, prepare 1:1s, or rehearse pushback on a roadmap. Use it journey-wide whenever a human power asymmetry shapes what you can say in public versus private, not only during formal project management tasks.1.3kinstalls75Engineering CultureEngineering Culture is a reference agent skill drawn from Lenny’s Podcast guest corpus for builders who want practitioner-backed culture tactics without hiring an org-design consultant. It packages memorable quotes—Duolingo-style experiment velocity, Shopify-era GitHub PM, Chip Huyen on problem scale—with short insights and tactical bullets you can translate into team norms, README governance, or agent session rules. The skill does not install tooling; it gives language and patterns for how often you ship experiments, whether non-engineers touch deploy paths, and how to prioritize system thinking over hero coding. Journey-wide, you can invoke it when you are still ideating on team shape, while building, before launch crunch, or when operating a growing solo business that is about to hire.first collaborator. It complements execution skills by answering how the work should feel day to day, not what file to edit next.1.3kinstalls76Onboarding New HiresOnboarding New Hires is a research-style agent skill from the Lenny-skills corpus: curated quotes, insights, and tactical advice from podcast guests on how new hires should ramp. It is aimed at solo builders and indie leads who are about to add a PM, engineer, or contractor and want proven patterns instead of generic HR checklists. The material emphasizes listening tours in the first 30 days, a summarized ‘state of the union,’ a few early wins without breaking culture, and publishing how you think so newcomers self-onboard before day one. It is not an automated HR system or legal compliance pack—it is procedural knowledge you invoke when planning role scope, manager expectations, and the first-quarter narrative. Use it during hiring decisions and the week before start date, then again when drafting onboarding docs or 1:1 cadences. Pair with your own company handbook; the skill supplies guest-validated mental models and concrete rituals that make small-team onboarding feel intentional rather than chaotic.1.3kinstalls77DogfoodingDogfooding is an agent skill that helps solo builders and small product teams implement disciplined eat-your-own-dogfood practices using patterns from operators who built teams around daily self-use of their own tools. You invoke it when you need your team (or yourself) to use the product intensely before betting the roadmap, when you are designing internal usage programs, or when you want stronger user empathy than interviews and dashboards alone provide. The skill walks through assessing current state, then applying leadership-backed frameworks: requiring creators and product folks to experience the same friction users feel, and treating “we would not use this” as a ship gate. It fits indie SaaS, agent products, and content tools where the builder wears every hat but still needs a repeatable ritual so feature work stays grounded in realism rather than speculation.1.3kinstalls78Running Effective 1 1sRunning Effective 1:1s is a Prism agent skill that packages curated Lenny Podcast guest insights into actionable rituals for managers and indie leads who still run people processes themselves. It is for solo builders and small-team founders who have direct reports or core contractors and want 1:1s to improve performance and trust—not fill a calendar slot. The skill contrasts two schools of practice: Hilary Gridley’s emphasis on monitoring joy, recovery, and behavioral activations so burnout does not masquerade as a slump, and Howie Liu’s argument for shrinking default weekly rosters so you can respond to timely topics with higher-quality, relationship-building catch-ups. Use it when you are starting a team, your 1:1s feel repetitive, or you suspect morale issues are hiding under “fine.” Plain-language guidance—no integrations—so any coding agent can apply the patterns to your next 1:1 agenda or team operating cadence.1.3kinstalls79Finding Mentors SponsorsFinding Mentors & Sponsors is an agent skill for indie and solo builders who need structured help turning vague “find a mentor” goals into actionable relationship design. It walks you through clarifying whether you want advice, advocacy, or accountability, then identifies realistic candidates slightly ahead on your path and coaches a low-friction outreach style based on specific asks rather than heavyweight mentor contracts. The workflow emphasizes sponsors who bet professional and social capital on you—often more impactful than passive mentors—for accelerating distribution, hiring, fundraising, or strategic pivots. You get principles for follow-up, reciprocity, and sustaining trust over quarters, which fits builders who operate alone and cannot rely on internal corporate programs. Use it when you are stuck on career or company decisions, want senior perspective on product or growth bets, or need an advocate inside a community, accelerator, or customer organization.1.2kinstalls80Sales CompensationSales Compensation is an agent skill that walks solo founders and small teams through designing sales pay plans that match how they actually sell and retain customers. It is built for moments such as hiring the first quota-carrying rep, restructuring an existing plan, or fixing incentive problems where reps optimize for bookings instead of healthy accounts. The skill asks about sales cycle length, average contract value, and retention patterns, then helps translate those constraints into OTE structure, variable pay, quotas, and new-hire ramp. It contrasts the common 50/50 base-and-bonus starting point with modern alignment ideas that reward net dollar retention and long-term customer outcomes, not only logo closes. Use it when comp feels stuck in “stone age” rules that fight your business model, so you get a conversational design pass you can take to finance or legal for final numbers.1.2kinstalls81Managing Imposter SyndromeManaging Imposter Syndrome is an agent skill that helps solo and indie builders work through inadequacy, fraud anxiety, and confidence dips when stepping into harder roles or bigger bets. It is for anyone who doubts qualifications, fears being exposed, or feels they do not belong—especially during fast growth periods that leaders describe as the most intense learning windows. Invoke it when self-doubt blocks decisions, slows shipping, or amplifies stress after a launch or promotion. The skill follows a short coaching flow: normalize the experience, reframe discomfort as growth signal, pinpoint the exact fear, then co-create practical strategies for when feelings spike. It does not replace therapy or HR programs; it offers structured, conversation-first reframing drawn from operator wisdom so you can keep building without mistaking stretch for failure.1.2kinstalls82Marketplace LiquidityMarketplace Liquidity packages guest insights from Benjamin Lauzier, Dan Hockenmaier, Ramesh Johari, and Tim Holley into a single reference for solo and indie builders who operate or are scoping two-sided products. It treats liquidity as how often buyers and sellers can complete the transaction they came for, with tactical notes on fragmentation, uniform needs, fill rates, and reallocating inventory when one side of the market lags. The material is research-grade strategy—not an install-and-run automation—meant to inform pricing, geographic rollout, category expansion, and where to concentrate growth effort when the marketplace feels empty on either side. Use it when you are validating whether a marketplace idea can ever thicken, designing launch sequencing (supply-first vs demand-first), or diagnosing stalled growth after launch. It complements analytics dashboards by giving vocabulary and mental models operators can cite in roadmaps and investor updates without replacing your own data.1.2kinstalls83Media Relationsmedia-relations is a Lenny-skills playbook that helps solo founders and indie operators treat press as a repeatable craft, not a one-off Hacker News post. The agent walks users through understanding what coverage they want, shaping a genuinely newsworthy angle, identifying the right reporters or freelancers, and managing relationships over time—including when to offer exclusives and how to stagger them. It synthesizes tactical quotes and frameworks from product leaders who have run real outreach programs, emphasizing preparation before volume pitching. Use it when you are nearing a launch or promoting a milestone and need structured coaching instead of generic “write a press release” advice. It pairs naturally with positioning and launch planning work but stays focused on journalist dynamics, pitch quality, and relationship norms that general marketing skills often skip.1.2kinstalls84Team Ritualsteam-rituals is a Lenny-skills agent package that helps solo founders and small teams turn fuzzy “we need better communication” goals into concrete, repeatable rituals. Grounded in insights from Lane Shackleton and Shishir Mehrotra, it treats rituals as the engine of team performance—not decoration—and applies the golden rituals test: every ritual must have a name, a template everyone can run, and recognition so new hires know them by their first Friday. The workflow begins by clarifying which behavior or outcome you want (alignment, decision speed, customer signal, etc.), then maps frameworks and named examples from the guests before you codify your own version. It fits indie builders who are hiring their first teammates or scaling from async DMs to a real operating rhythm. Unlike generic culture advice, the skill pressures you to keep a short list of high-leverage rituals instead of an endless meeting calendar, which preserves focus while you still ship product.1.2kinstalls85Running OffsitesRunning Offsites translates Lenny’s Podcast operating playbooks into an agent-guided planning workflow for indie and remote-first teams. You start by naming the outcome—strategy clarity, trust, quarterly planning—and only then design session mix, bursts vs. full retreats, and logistics that remove friction instead of creating heroics. The skill emphasizes quarterly in-person creative bursts for distributed teams, separating high-bandwidth collaboration from default Slack cadence, while warning when interpersonal debt means an offsite will backfire without pre-work. It fits founders with three to fifteen contributors who cannot afford a corporate event planner but still need Shopify-grade intentionality. Deliverables are agendas with purpose-tagged blocks, readiness notes, and connection vs. work balance—not venue booking automation.1.2kinstalls