plugins/pm-finance/skills/investor-pitch-deck/SKILL.md
Build the narrative and slide structure for an investor pitch deck. Use when asked to create a pitch deck, investor presentation, fundraising deck, or startup pitch. Produces a slide-by-slide structure with narrative beats, key messages, and what each slide must prove to an investor.
npx skillsauth add mohitagw15856/pm-claude-skills investor-pitch-deckInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Builds the complete narrative and slide structure for an investor pitch deck — focused on what investors need to see, not what founders want to show.
For each slide:
Slide 1: Cover — Proves you can say what you do in one sentence. Slide 2: Problem — Proves the problem is real, painful, and large. Lead with the human problem, not market size. Slide 3: Solution — Proves your solution is meaningfully better. Focus on outcome, not features. Slide 4: Product — Proves this is real and works. Show the actual product. Slide 5: Traction — Proves people want this. Show retention and revenue, not signups. Slide 6: Market — Proves the market is large enough. Use bottoms-up TAM where possible. Slide 7: Business Model — Proves you understand unit economics. Include CAC and LTV. Slide 8: Go-To-Market — Proves you can acquire customers efficiently. Focus on what is actually working. Slide 9: Competition — Proves you understand the landscape. Never say "no competitors." Slide 10: Team — Proves this team can execute this opportunity. One sentence per person, specific. Slide 11: Financials — Proves you understand your business. Show assumptions, not just projections. Slide 12: The Ask — Proves you know exactly what you need. Specific use of funds and 18-month milestones.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.