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

presentation-builder

Transform ideas, outlines, or documents into structured slide content with clear titles, bullet points, and speaker notes. Adapts to presentation type (pitch decks, business reviews, technical workshops, educational talks). Use when user says "create slides", "build a deck", "pitch deck", "presentation structure", "talk structure", "keynote", "slide deck", "conference talk", or needs slide content for any format. Also trigger when user has content they want to present to an audience - even if they don't explicitly say "presentation" or "slides". To produce a branded .pptx file, see ppt-maker.

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

연동 도구PowerPoint
설치 방법 보기

포함된 파일(1)

  • SKILL.md3.7 KB

SKILL.md(원문)

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

Presentation Builder

How It Works

Step 1: Gather Inputs

Ask the user:

  1. Audience - Who is in the room? (investors, team, clients, community)
  2. Duration - How long? (5 min = 5-7 slides, 15 min = 12-15 slides, 30 min = 20-25 slides)
  3. Purpose - What decision or action should the audience leave with?
  4. Content - What does the user have? (raw notes, doc, outline, or just a topic)

Step 2: Select Structure Template

Pitch Deck (investors, sponsors): Problem > Solution > Market Size > How It Works > Traction/Proof > Team > Ask

Business Review (leadership, stakeholders): Context > Performance vs. Goal > Key Findings > Risks/Blockers > Decisions Needed > Next Steps

Technical Workshop (practitioners): Problem Definition > Concepts > Demo/Walkthrough > Common Pitfalls > Hands-On Exercise > Key Takeaways

Educational Talk (community, general audience): Hook/Story > Core Idea > Evidence/Examples > Implications > What To Do Next

Step 3: Generate Slide Content

For each slide:

  • Title: 5-10 words, states the takeaway - not the topic
    • Weak: "Market Overview" - Strong: "TAM is $4B and growing 30% YoY"
  • Bullets: 3-5 max. If you have 8 bullets, you have 2 slides.
  • Visual placeholder: [IMAGE: description of what visual would go here]
  • Speaker note: 1-2 sentences of what to say out loud (include only if requested)

Step 4: Output Format

Deliver as numbered slides in markdown:

## Slide 1: [Title]
- Bullet 1
- Bullet 2
- Bullet 3
[IMAGE: description]
Speaker note: ...

After the slides, add:

  • Slide count and estimated time at a comfortable pace
  • One sentence on the best tool for rendering (Gamma for visual polish, Google Slides for collaboration, Canva for design flexibility)

Rules

  • Keep slides to 3-5 bullets. Beyond 5, the audience reads instead of listening - the slide competes with the speaker instead of supporting them.
  • Every slide title must state a takeaway, not a label. Audiences remember "Revenue grew 40% in Q3" but forget "Revenue Update." A takeaway title means even someone skimming the deck gets the story.
  • If the user's content has more material than slides allow, recommend what to cut. Cramming dilutes every point - a focused deck with 12 strong slides beats 20 slides where half are filler.
  • Slide count = duration in minutes / 2 (rough guide; adjust for content density).

Anti-Patterns

1. Wall-of-text slide Bad: A slide with 8 bullets and a paragraph of context underneath Good: Split into two slides, each with 3-4 bullets that the speaker elaborates on verbally

2. Label title Bad: "Market Overview" Good: "TAM is $4B and growing 30% YoY"

3. Reading the slides Bad: Speaker notes that repeat the bullet text word for word Good: Speaker notes that add context, stories, or data the bullets don't show

4. Everything-in-the-deck Bad: 30 slides for a 15-minute talk because "the content is important" Good: 12 slides for the talk, appendix slides for the Q&A backup

5. Decoration over clarity Bad: Complex charts with 6 data series and no callout Good: One chart, one trend line highlighted, one takeaway in the title

리뷰

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

댓글

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

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

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. 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의 스킬 모두 보기

이 스킬의 문제 신고