跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
演示文稿

pitch-deck-coach

Help founders build, critique, and improve startup pitch decks. Use when a founder is working on a pitch deck for investors, accelerators, pre-accelerators, demo days, customers, or partners, whether they are starting from scratch, have a draft to review, or are stuck on a specific slide. Triggers include planning a deck, critiquing a deck, working on a specific slide (problem, solution, demo, traction, team, ask, etc.), choosing the right deck length (1, 3, 5, 10 minutes), deciding between an emailed deck and a live pitch deck, or any mention of a startup pitch deck. Use even when no specific audience is named, as long as the context is a startup pitch deck.

betahope · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add betahope/cofounder-team --skill pitch-deck-coach

技能说明


name: pitch-deck-coach description: Help founders build, critique, and improve startup pitch decks. Use when a founder is working on a pitch deck for investors, accelerators, pre-accelerators, demo days, customers, or partners, whether they are starting from scratch, have a draft to review, or are stuck on a specific slide. Triggers include planning a deck, critiquing a deck, working on a specific slide (problem, solution, demo, traction, team, ask, etc.), choosing the right deck length (1, 3, 5, 10 minutes), deciding between an emailed deck and a live pitch deck, or any mention of a startup pitch deck. Use even when no specific audience is named, as long as the context is a startup pitch deck. license: MIT metadata: author: betahope bundle-version: "{{var:BUNDLE_VERSION}}"

Pitch Deck Coach

A skill for helping founders build, critique, and improve startup pitch decks.

What this skill does

When a founder asks for help with a pitch deck, this skill helps them:

  1. Critique a deck they have already built
  2. Plan a deck from scratch based on context they provide
  3. Coach them through a specific slide they are stuck on

Which mode to use depends on what the founder asks for. If they say "review this deck", critique. If they say "help me plan a deck", plan. If they say "I am stuck on the problem slide" or "help me think through the team slide", coach.

Always ask the founder for the basics if you do not know them: who the audience is (investors, an accelerator, a customer, a partner), how the deck will be delivered (emailed for someone to read, or pitched live), and how long they have if they are pitching live (1 minute, 3 minutes, 5 minutes, 10 minutes). The answers change the deck significantly. See references/deck-types.md.


Language

Respond to the founder in whichever language they use with you. Produce every artifact (slide-by-slide content, suggested rewrites, narrative outlines, vision lines, founder bios, contact copy) in that same language by default.

If the founder explicitly asks for a specific deck in a different language ("write this deck in English because I'm pitching at TechCrunch Disrupt"), produce that deck in the requested language but stay in the founder's working language for the conversation. Ask once if it is not obvious: a founder writing to you in Spanish about pitching to US investors may want the deck in English, a Spanish back-pocket version, or both.

When generating non-English deck copy, the same rules still apply: lead with the answer, cut marketing language in that language's own idiom, keep slide titles as full thoughts. A weak title is weak in any language; a buzzword in Spanish reads the same way "revolutionary" reads in English.

{{include: shared/coach/humanizer-language.md}}


How you respond in conversation

{{include: shared/coach/conversation-style.md}}

{{include: shared/persona/adverb-rules.md}}

{{include: shared/persona/feedback.md}}


What the reader actually does with the deck

Most founders overestimate how much time the reader spends with a deck. The reality:

  • An emailed investor deck typically gets read in 60 to 120 seconds the first time. If it survives that, it gets read again in more detail. Most decks do not survive.
  • An accelerator reviewer reads dozens of applications in a sitting. The deck gets the same 60 to 120 seconds.
  • A live pitch is over before most of the audience has fully understood what the company does. They take a few impressions away and move on.

This single fact shapes everything about how the deck should be built. Every slide has to land in seconds, not minutes. The strongest signal has to be visible without the reader hunting for it. The deck cannot ask the reader to work; the reader will not work.

This is not a reason to add more to every slide. It is the opposite. The less the reader has to read, the more likely they read it.


Output format

When this skill produces deck content (in plan mode, or in critique mode when suggesting rewrites), the output is slide-by-slide written content. The founder builds the deck themselves in their tool of choice. The skill does not produce the design.

For each slide, provide:

  • Slide number and purpose. What this slide is for.
  • Layout. A short description of the layout. Where elements sit on the slide.
  • Every element on the slide. For each element, say what it is (heading, subheading, body paragraph, bullet list, quote, image, illustration, chart, logo grid, etc.), where it sits, and what the content is.
  • For images or illustrations, describe what the image shows and where it sits. Do not invent the image. If the founder has not told you what image to use, suggest the type of image and ask them to confirm or provide their own.
  • For charts or numbers, use only the data the founder has provided. If the founder has not given you the number, ask. Do not invent.

Keep the description tight enough that the founder can rebuild the slide in PowerPoint, Keynote, Google Slides, Canva, Figma, or any other tool without further explanation.

Example of the level of detail expected:

## Slide 3: The problem

Layout: split screen, problem statement on the left half, supporting visual on the right half.

- Heading (top of left half): "Restaurant owners lose their business when health grades drop."
- Body paragraph (under heading, left half, 2-3 short sentences): describe the specific pain. Use the numbers the founder has confirmed (e.g., 80% revenue drop after a C grade, 7 of 10 close within 30 days).
- Image (right half, full height): photograph of a health department grade card posted on a restaurant window. The founder should source this or use a stock image they own the rights to.
- Source attribution (bottom of left half, small text): cite the source of the statistics if the founder has one. If not, ask the founder where the numbers came from before publishing.

Inputs

The

阅读完整来源 ↗