본문으로 건너뛰기
cccskills
무료GitHub에 공개

pitch-narrative

Use when the user says "write my pitch", "help me tell my startup story", "craft my investor narrative", "why now slide", "what's our secret", "how do I explain what we do", "make my pitch compelling", "pitch deck story", "elevator pitch", "why will we win", "contrarian insight", or wants to build a persuasive, coherent narrative around their startup for investors, press, or recruiting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md6.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Overview

Based on "Zero to One" by Peter Thiel. The core principle: every great business is built on a secret - a true belief about the world that most people disagree with or have not yet seen. A compelling pitch narrative does not start with market size or traction; it starts with the insight that makes [your startup] inevitable. Investors do not fund companies - they fund theories about the future.

Workflow

Step 1: Find the secret

Answer this question before writing a single slide or sentence:

"What important truth do very few people agree with you on?"

This is Thiel's core question from Zero to One. Your answer must be:

  • Specific (not "AI is going to change everything")
  • Contrarian (a smart person would push back)
  • Defensible (you have a reason to believe it that others lack)

Examples of weak secrets: "The market is big." / "Customers want something better." Examples of strong secrets: "Enterprise compliance teams do not actually want automation - they want audit trails, and no one is selling that." / "[Your industry] has a structural cost problem that incumbents cannot fix without destroying their existing revenue."

Write the secret in one sentence. Everything else in the pitch should follow from it.

Step 2: Build the "Why Now" argument

Thiel asks: if this was a good idea, why hasn't it been built already? Your narrative must answer this.

Identify what changed recently:

  • A technology that became available or cheap (APIs, models, infrastructure)
  • A regulatory shift
  • A behavior change in the customer (remote work, a platform's API opening/closing)
  • A market structure change (incumbent collapsed, new distribution opened)

Frame it as: "For the last [X] years, [problem] existed but [constraint] made it unsolvable. [Specific change] in [year] removed that constraint. This is the window."

If you cannot answer "why now", the narrative will feel academic rather than urgent.

Step 3: Define your monopoly thesis

From Zero to One: competition is for losers. Great companies build and defend monopolies. Your pitch should show investors the path to one.

Pick your monopoly type:

  • Proprietary technology: 10x better on a measurable dimension (not "better UX")
  • Network effects: each additional user makes the product more valuable for all users
  • Economies of scale: fixed costs that become a structural advantage as you grow
  • Brand: takes years to build and cannot be copied quickly

State explicitly which type you are building toward and why [your startup] is uniquely positioned to achieve it. Generic "we have a great team and product" does not count.

Step 4: Sequence the narrative

The narrative arc (for pitch deck, investor memo, or verbal pitch):

  1. The secret: the contrarian insight about the world
  2. The problem: what breaks because most people have not acted on this insight yet
  3. Why now: the specific change that opened the window
  4. The solution: how [your product] captures the opportunity the insight creates
  5. The monopoly path: what unfair advantage compounds over time
  6. The ask: what you need and what it unlocks

Do not lead with the problem. Lead with the secret. Investors hear hundreds of problem statements. A sharp contrarian insight stops them.

Keep each section to 2-3 sentences when pitching verbally. Expand for written memos.

Step 5: Stress-test the narrative

Ask these questions before sharing the pitch:

  • "What would a smart skeptic say is wrong with our secret?" (If you cannot steelman the objection, your secret is not sharp enough.)
  • "Would a reasonable person in [your industry] disagree with our Why Now?" (If they would agree too easily, it is not a secret.)
  • "Is our monopoly path specific to us, or could any well-funded competitor replicate it in 12 months?"

Revise based on the weakest answers.

Step 6: Write the one-paragraph version

Compress the entire narrative into a single paragraph. This is your verbal pitch, your email opening, and your Twitter/LinkedIn bio.

Format: "[Your startup] is built on a belief that [secret]. [Why now in one sentence]. We [what the product does] in a way that [monopoly advantage]. We are raising [amount] to [specific milestone that proves the thesis]."

If this paragraph does not hold together without the longer pitch behind it, the narrative is not tight enough yet.

Anti-Patterns

1. Leading with market size Bad: "This is a $50B market and we are going after 1%." Good: "Most people believe X, but we believe Y - and that difference is worth $50B."

2. Weak secrets disguised as insights Bad: "Customers are underserved by existing solutions." Good: "Existing solutions are bad by design - incumbents profit from the inefficiency we're eliminating."

3. Solution-first storytelling Bad: Describing the product features before establishing why the insight is true. Good: Making the listener believe the secret before showing them the product.

4. Vague monopoly claims Bad: "We have a first-mover advantage and strong network effects." Good: "Every enterprise we onboard adds [specific data] to our model, which reduces [specific cost] by [X%] - an advantage that grows geometrically and cannot be replicated from a cold start."

Quality Checklist

  • The secret is stated in one sentence and a smart person would push back on it
  • "Why now" cites a specific event or change with a date or timeframe
  • Monopoly type is named explicitly (technology, network effects, scale, or brand)
  • Narrative sequence is: secret - problem - why now - solution - monopoly - ask
  • The one-paragraph version works standalone without the longer pitch
  • The strongest objection to the secret is addressed inside the narrative
  • No slide or sentence leads with market size before establishing the insight

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

qa-aman의 스킬 모두 보기

이 스킬의 문제 신고