Token导航 LogoToken导航

Agent Skill · 研究检索

pitch-deck-builder(融资演讲稿构建者)

pitch-deck-builder 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

pitch-deck-builder 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 63,891。

总安装 309周安装 13GitHub Stars 28下载 108核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:pitch-deck-builder(融资演讲稿构建者)
来源仓库:https://github.com/exploration-labs/nates-substack-skills
仓库路径:skills/pitch-deck-builder
安装命令:
npx skills add https://github.com/exploration-labs/nates-substack-skills --skill pitch-deck-builder
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/exploration-labs/nates-substack-skills --skill pitch-deck-builder

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于根据关键词、任务场景或来源线索进行信息核验和用法确认。可结合来源仓库和原始 README 继续验证具体用法和适用条件。安装前建议确认权限范围、维护状态,以及是否会触发联网或命令执行。

使用前应确保具备授权,避免对未授权系统执行敏感操作。

来源仓库内路径:skills/pitch-deck-builder

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/exploration-labs/nates-substack-skills --skill…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

pitch-deck-builder 怎么安装?

在终端执行 npx skills add https://github.com/exploration-labs/nates-substack-skills --skill pitch-dec…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

pitch-deck-builder 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

pitch-deck-builder 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

pitch-deck-builder 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

pitch-deck-builder 用的人多吗?

公开数据是累计安装 309 次,近一周安装 13 次,下载 108 次,GitHub 28 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

pitch-deck-builder 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
pitch-deck-builder

融资演讲稿构建者 · 本页

30928只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Pitch Deck Builder

This skill provides a comprehensive workflow for creating professional pitch decks through conversational discovery, narrative structuring, and technical execution with context-aware best practices.

Overview

Creating effective pitch decks requires balancing compelling storytelling with strategic information architecture. This skill guides the process from initial concept through final presentation, with special attention to:

  • Conversational discovery to extract key business insights
  • Narrative arc construction that resonates with target audiences
  • Modern, uncluttered slide design that emphasizes clarity
  • Token-aware chunking strategies to prevent context window overflow
  • Iterative refinement based on presentation goals

When to Use This Skill

Use this skill when:

  • Creating investor pitch decks or fundraising presentations
  • Building sales decks or business presentations
  • Developing product launch presentations
  • Crafting founder or team introductions
  • Any scenario requiring strategic narrative presentation of business concepts

Core Workflow

Phase 1: Discovery Interview

CRITICAL: Before creating any slides, conduct a structured discovery interview to understand the pitch requirements. This prevents wasted effort and ensures the final deck aligns with user goals.

The discovery process should be conversational and adaptive, not a rigid questionnaire. Ask 2-3 questions at a time, then build on responses naturally. Focus on understanding the story before collecting details.

Stage 1: Foundation (3-5 questions)

Start with high-level questions to understand the pitch context:

  1. Pitch Type & Audience: "What type of pitch deck are you creating, and who's the primary audience? For example: pre-seed investors, enterprise customers, strategic partners, internal stakeholders, etc."
  2. Core Narrative: "In 2-3 sentences, what's the most compelling story you want to tell? Think about the transformation or opportunity you're presenting."
  3. Stage & Goals: "What stage is your company/product at, and what's your goal for this deck? For example: raising $2M seed round, closing enterprise deals, securing partnerships, etc."
  4. Key Constraints: "Are there any specific constraints I should know about? For example: must be under 15 slides, needs to address specific concerns, follows a particular format, etc."
Stage 2: Business Fundamentals (5-8 questions)

Based on initial responses, dive into the business model and value proposition:

  1. Problem Definition: "Describe the problem you're solving. What pain point exists today, and how acute is it for your target customers?"
  2. Solution Approach: "What's your solution, and why is it uniquely positioned to solve this problem? What's your unfair advantage?"
  3. Market Opportunity: "What's the market size and your addressable segment? Are there any particularly compelling market dynamics or timing factors?"
  4. Business Model: "How do you make money? What are your unit economics or revenue model?"
  5. Traction & Validation: "What traction or validation do you have? This could be revenue, users, partnerships, pilot results, etc."
  6. Competition: "Who are your main competitors or alternatives, and how are you differentiated?"
Stage 3: Narrative Elements (4-6 questions)

Gather the elements needed to craft a compelling narrative:

  1. Founding Story: "Is there a compelling founding story or insight that led to creating this company/product?"
  2. Customer Evidence: "Do you have any customer quotes, case studies, or success stories that illustrate your impact?"
  3. Vision: "What's your long-term vision? Where do you see this in 3-5 years?"
  4. Team: "What makes your team uniquely qualified? Any notable backgrounds, expertise, or relevant achievements?"
  5. Milestones: "What are your key milestones or roadmap items for the next 12-18 months?"
Stage 4: Data & Materials (3-4 questions)

Collect specific data points and existing materials:

  1. Quantitative Data: "What are your key metrics or numbers? For example: revenue, growth rate, user count, retention, CAC/LTV, margins, etc."
  2. Visual Materials: "Do you have any existing materials I should incorporate? For example: logos, brand colors, product screenshots, team photos, existing slides, etc."
  3. Must-Include Elements: "Are there any specific slides, data points, or messages that absolutely must be included?"
Context Window Management Strategy

BEFORE proceeding to Phase 2, assess the context implications:

  1. Calculate estimated token usage:

- Discovery interview: ~2,000-4,000 tokens - Narrative planning: ~1,500-3,000 tokens - Slide content creation: ~500-800 tokens per slide - Technical execution: ~3,000-5,000 tokens - Base overhead: ~2,000 tokens

  1. Identify chunking needs:

- If deck > 15 slides: STRONGLY RECOMMEND chunking strategy - If deck > 20 slides: REQUIRE chunking strategy - If user provides extensive existing content: Consider chunking

  1. Propose chunking approach (if needed): "Based on your requirements, we're looking at approximately [X] slides. To maintain quality and avoid context constraints, I recommend we build this deck in [2-3] phases: We'll create each phase completely, then combine them at the end. This ensures every slide gets proper attention and design quality. Does this approach work for you?"

- Phase 1: Opening slides (Cover, Problem, Solution, Product) - slides 1-[X] - Phase 2: Business slides (Market, Business Model, Traction, Competition) - slides [X]-[Y] - Phase 3: Closing slides (Team, Financials, Milestones, Ask) - slides [Y]-[Z]

  1. Document phase boundaries: If using chunking, clearly document in narrative plan which slides belong to which phase

Phase 2: Narrative Planning

After completing discovery, create a detailed narrative plan that serves as the blueprint for the deck.

Step 1: Determine Slide Sequence

Based on pitch type and discovery insights, recommend an appropriate slide sequence. Common structures:

Standard Investor Pitch (12-15 slides):

  1. Cover slide (Company name, tagline, contact)
  2. Problem (The pain point)
  3. Solution (Your approach)
  4. Product/Demo (How it works)
  5. Market Opportunity (TAM/SAM/SOM)
  6. Business Model (Revenue streams)
  7. Traction (Metrics, growth)
  8. Competition (Landscape, differentiation)
  9. Go-to-Market (Distribution, customer acquisition)
  10. Team (Founders, key hires)
  11. Financials (Projections, unit economics)
  12. Milestones (12-18 month roadmap)
  13. Funding Ask (Amount, use of funds)
  14. Vision (Long-term impact)
  15. Contact/Thank You

Product Pitch (8-12 slides):

  1. Cover
  2. Problem
  3. Solution Overview
  4. Product Details/Demo
  5. Benefits & ROI
  6. Customer Success Stories
  7. Competitive Advantage
  8. Pricing/Packages
  9. Implementation
  10. Team/Company
  11. Next Steps
  12. Contact

CRITICAL: Adapt the sequence based on discovery insights. If the user has exceptional traction, move that slide earlier. If the team is the strongest asset, elevate it. The narrative should build momentum toward the most compelling elements.

Step 2: Create Detailed Content Outline

For each slide, document:

  1. Slide title: Clear, assertive statement (not generic labels)
  2. Core message: The single most important point this slide must convey
  3. Supporting points: 2-4 key facts, data points, or arguments (bullet form)
  4. Visual strategy: How this slide should be visually presented
  5. Speaker notes: 1-3 sentences the presenter should say about this slide
  6. Data requirements: Specific numbers, percentages, or facts needed

Example outline entry:

Slide 7: "We've Grown 40% Month-Over-Month for 6 Months"

Core message: Our consistent growth demonstrates product-market fit and validates our approach

Supporting points:
- 10,000+ active users, up from 500 six months ago
- 85% of users remain active after 30 days (industry benchmark: 25%)
- NPS score of 72 (promoter-heavy user base)
- Zero paid marketing spend - all organic and referral growth

Visual strategy: Large growth chart showing MoM trajectory, with key metrics callouts around it

Speaker notes: "This isn't a spike - it's sustained, compounding growth driven by genuine product love. Our users are becoming our sales team, and retention numbers show they're staying because we're solving a real problem for them."

Data requirements: Monthly user count for last 6 months, retention cohort data, NPS score
Step 3: Validate Narrative Arc

Review the complete outline and validate:

  1. Opening strength: Do the first 3 slides hook attention and establish credibility?
  2. Logical flow: Does each slide build naturally to the next?
  3. Peak placement: Is the strongest material positioned for maximum impact (typically slides 6-9)?
  4. Emotional resonance: Are there moments of human connection (customer stories, founding insight, vision)?
  5. Objection handling: Are likely concerns addressed before they become barriers?
  6. Clear ask: Is the call-to-action unambiguous and compelling?

Present the complete narrative outline to the user for approval before proceeding to design. Make it easy to review by presenting in a clear, scannable format.

Phase 3: Design & Technical Execution

Once the narrative plan is approved, execute the technical creation using the pptx skill and html2pptx workflow.

Design Principles

CRITICAL: Pitch decks must balance professionalism with visual impact. Follow these principles:

  1. Whitespace is strategic: Each slide should have 40-60% whitespace. Crowded slides lose impact.
  2. One idea per slide: If a slide tries to communicate multiple ideas, split it into multiple slides.
  3. Typography hierarchy:

- Headlines: Large (36-48pt), bold, assertive statements - Body text: Readable (18-24pt), limited to 3-5 bullets maximum - Data callouts: Extra large (48-72pt) for key numbers - Avoid paragraphs: Use bullet points, but even better - use short phrases

  1. Color strategy:

- Primary: Brand color for key elements and data visualization - Accent: Complementary color for highlights and emphasis - Neutral: Dark gray (not black) for body text, light gray for backgrounds - Limit palette to 3-4 colors total

  1. Data visualization:

- Prefer charts over tables when showing trends - Use large, simple charts with clear labels - Highlight the key insight (annotate charts with the "so what?") - Remove chart junk - no 3D effects, excessive gridlines, or decorative elements

  1. Layout patterns:

- Full-bleed: Image or color background with text overlay (cover, section dividers) - Two-column: Text on left, visual on right (most content slides) - Centered: Single key message or data point (impact slides) - Grid: Multiple items of equal importance (team, customers, features)

Technical Implementation

IMPORTANT: Read /mnt/skills/public/pptx/SKILL.md completely before beginning slide creation. The pptx skill contains critical requirements for html2pptx workflow.

Follow this execution sequence:

  1. Read pptx skill documentation: view /mnt/skills/public/pptx/SKILL.md (no range limits - read entire file)
  2. Read html2pptx documentation: view /mnt/skills/public/pptx/html2pptx.md (no range limits - read entire file)
  3. Install html2pptx if needed: Verify installation with npm list -g @ant/html2pptx and install if necessary
  4. Create shared CSS file: Define CSS variables for colors, typography, and spacing that will be used across all slides
  5. Create HTML files for each slide:

- Use proper dimensions (960px × 540px for 16:9) - Embed shared CSS in <style> tags - Use semantic HTML (<h1>, <p>, <ul>, etc.) - Use row/col/fit classes for layout (NOT flexbox) - Apply CSS variables consistently - Include class="placeholder" for chart/table areas

  1. Create conversion script: Write JavaScript to convert HTML to PPTX using html2pptx library and PptxGenJS
  2. Execute and validate: Run the conversion script and generate thumbnail grid for visual validation
  3. Iterate if needed: Fix any layout issues, text overflow, or visual problems identified in thumbnails
Chunking Execution Strategy

If using a multi-phase approach (recommended for >15 slides):

  1. Phase execution:

- Build Phase 1 completely (HTML + PPTX generation + validation) - Save Phase 1 output to /mnt/user-data/outputs/ - Begin new conversation or clear context - Load Phase 1 PPTX and narrative plan - Build Phase 2 (append to existing PPTX) - Repeat for remaining phases

  1. Phase handoff checklist:

- Save phase PPTX file to outputs - Save narrative plan for next phase - Save CSS file for design consistency - Document any design decisions or patterns established - Note current slide number for next phase

  1. Combination approach:

- After all phases complete, combine using Python-PPTX or manual merge - Validate slide numbering and transitions - Generate final thumbnail grid - Check for design consistency across all slides

Phase 4: Refinement & Delivery

After initial creation, support iterative improvement:

  1. Visual review: Generate and examine thumbnail grid for layout issues
  2. Content refinement: Offer to adjust messaging, data presentation, or narrative flow based on feedback
  3. Design iteration: Make styling adjustments, color changes, or layout modifications
  4. Export preparation: Ensure final PPTX is in /mnt/user-data/outputs/ with clear filename
  5. Usage guidance: Provide brief tips for presenting the deck effectively

Best Practices

Discovery Quality

  • Listen more than prescribe - let the user's story emerge naturally
  • Ask "why" and "so what" to uncover deeper insights
  • Notice what the user emphasizes - these are often the strongest narrative elements
  • Validate understanding by reflecting back key points

Narrative Construction

  • Start with why, not what - establish emotional connection before details
  • Use assertive slide titles that make claims, not generic labels ("We're Growing 40% Monthly" not "Traction")
  • Place the strongest material in the middle third of the deck (slides 6-9 in a 15-slide deck)
  • End with clarity on the ask and vision for impact

Design Execution

  • When in doubt, remove elements rather than add them
  • Use data visualization to replace bullet points whenever possible
  • Test readability by viewing slides at thumbnail size - key points should still be clear
  • Maintain consistent spacing, alignment, and typography throughout

Context Management

  • Propose chunking early if deck will exceed 15 slides
  • Document design decisions in CSS comments for phase consistency
  • Save phase outputs immediately to prevent context loss
  • Keep narrative plan accessible across phases

Common Pitch Deck Types

Investor Pitch (Pre-Seed/Seed)

  • Focus: Team, problem, early traction
  • Length: 12-15 slides
  • Tone: Ambitious but realistic, founder-driven
  • Key slides: Problem, solution, why now, founding story, early metrics

Investor Pitch (Series A+)

  • Focus: Growth metrics, business model, competitive moats
  • Length: 15-18 slides
  • Tone: Data-driven, scalable, market-leading
  • Key slides: Growth charts, unit economics, competitive landscape, market expansion

Sales/Product Pitch

  • Focus: Customer value, ROI, implementation
  • Length: 10-15 slides
  • Tone: Customer-centric, benefit-oriented, practical
  • Key slides: Problem/pain point, solution benefits, customer success, pricing, next steps

Partnership Pitch

  • Focus: Strategic alignment, mutual value, capabilities
  • Length: 8-12 slides
  • Tone: Collaborative, strategic, win-win
  • Key slides: Company overview, strategic fit, proposed partnership model, case for collaboration

References

For additional guidance on pitch deck best practices, narrative construction, and data visualization, see:

  • references/pitch-deck-best-practices.md - Comprehensive guide to effective pitch decks
  • references/data-visualization-guide.md - Chart types, design patterns, and storytelling with data
  • references/narrative-frameworks.md - Story structures and persuasion techniques

Technical Dependencies

This skill leverages the pptx skill for presentation creation. Ensure the following are available:

  • pptx skill at /mnt/skills/public/pptx/
  • html2pptx library (installed via npm)
  • python-pptx and related dependencies

All technical execution should follow the workflows documented in /mnt/skills/public/pptx/SKILL.md.

平台分布

Codex

37.73%
按下载量换算41

Claude

30.25%
按下载量换算33

Cursor

18.22%
按下载量换算20

Gemini CLI

10.5%
按下载量换算11

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills